In the context of increasingly complex corporate processes and the development of ever more sophisticated products, the management of corporate processes today must go beyond purely technical document approval in the PLM system.
Often, several employees from different teams have to be involved in the document review process. A wide variety of work situations and locations and finally a multitude of end devices and work methods must also be taken into account.
A clean process definition as well as the central control of the processes by a workflow engine offer enormous added value here.
The clarity and transparency in the process gained through the keytech workflow engine bring relief from the tedious organization of routine activities.
With the goal of making the benefits of the keytech workflow engine as simple and straightforward as possible for all our customers, we have developed the Standard Workflows. Standard orkflows are an easy way to get started with BPMN in keytech PLM & DMS and solve typical organizational issues in a straightforward way.
Standard workflows are characterized above all by the fact that they are particularly easy to implement in your existing keytech solution. They can be activated at the push of a button in the workflow admin. After that, only a few steps are required to use the new workflow in your solution.
Through the standard workflows, your existing configurations and customizations in keytech are merely supplemented and thus remain completely intact.
So you can continue to rely on the existing processes and customizations of your keytech solution and combine them with the standard workflows to solve new tasks in a simple and straightforward way.
The keytech elements relevant for the workflow are combined in a superordinate workflow folder.
It is the frame for all important elements.
This way, your existing keytech structures can be seamlessly integrated into the new standard workflows.
There are more and more regulations and documents that various employees in the company are required to have verifiably taken note of. It must therefore be documented that and when the corresponding users have read the document. With the standard workflow "Perusal", you can compile the relevant documents in a workflow folder and easily define the recipient group of the acknowledgement.
By starting the standard workflow "Perusal", the defined colleagues receive a task to read the document and confirm that this has been done. The notes in the workflow folder then record who completed this task and when, giving the initiator of the perusal an overview and ensuring that the entire process is neatly documented in the system.
In addition to the purely technical release of documents, a higher-level organizational document release is playing an increasingly important role, in which contact persons from different departments must be involved. In order to enable this release in a simple way, especially for employees who do not work with the keytech client, we have developed the standard workflow “Release”.
With the standard workflow “Release”, the documents relevant for the release can be compiled in a workflow folder and the release workflow can be started. The BPMN process then allows parallel release by several reviewers, who have the option in a workflow task to release the process or to store a comment for the initiator of the release. Following the organizational release, your technical release can take place as usual.
|__hssc||30 minutes||HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.|
|__hssrc||session||This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.|
|_GRECAPTCHA||5 months 27 days||Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks.|
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|CookieLawInfoConsent||1 year||CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.|
|elementor||never||The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time.|
|JSESSIONID||session||New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application.|
|PHPSESSID||session||This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.|
|__cf_bm||30 minutes||Cloudflare set the cookie to support Cloudflare Bot Management.|
|_icl_visitor_lang_js||1 day||WPML sets this cookie to store the redirected language.|
|drift_aid||1 year 1 month 4 days||Drift sets this cookie as a session identifier token. It is used to tie the visitor on your website to a current website session within the Drift system. This enables session-specific features, such as popping up a message only once during a 30 minute session to prevent a disruptive experience.|
|drift_campaign_refresh||30 minutes||Drift sets this cookie as a unique ID for the specific user. This allows the website to target the user with relevant offers through its chat functionality.|
|driftt_aid||1 year 1 month 4 days||Drift sets this cookie as an anonymous identifier token. As people come onto the site, they will get this cookie.|
|li_gc||5 months 27 days||Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.|
|lidc||1 day||LinkedIn sets the lidc cookie to facilitate data center selection.|
|UserMatchHistory||1 month||LinkedIn sets this cookie for LinkedIn Ads ID syncing.|
|wp-wpml_current_language||session||WordPress multilingual plugin sets this cookie to store the current language/language settings.|
|wpml_browser_redirect_test||session||This cookie is set by WPML WordPress plugin and is used to test if cookies are enabled on the browser.|
|__lotl||5 months 27 days||Lucky Orange sets this cookie to identify the traffic source URL of the visitor's original referrer, if any.|
|_lo_uid||1 year 1 month 4 days||Lucky Orange sets this cookie as a unique identifier for the visitor.|
|_lo_v||1 year||Lucky Orange sets this cookie to identify the total number of visitor's visits.|
|_lorid||10 minutes||Lucky Orange sets this cookie to record the current ID of visitors.|
|__hstc||5 months 27 days||Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).|
|_fbp||3 months||Facebook sets this cookie to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising after visiting the website.|
|_ga||1 year 1 month 4 days||Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.|
|_ga_*||1 year 1 month 4 days||Google Analytics sets this cookie to store and count page views.|
|_gcl_au||3 months||Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services.|
|_gd_session||4 hours||This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.|
|_gd_svisitor||1 year 1 month 4 days||This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program.|
|_gd_visitor||1 year 1 month 4 days||This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.|
|AnalyticsSyncHistory||1 month||Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.|
|CONSENT||2 years||YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data.|
|hubspotutk||5 months 27 days||HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.|
|ifso_visit_counts||1 year||If So sets this cookie to store number of visits.|
|ln_or||1 day||Linkedin sets this cookie to registers statistical data on users' behaviour on the website for internal analytics.|
|vuid||1 year 1 month 4 days||Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.|
|bcookie||1 year||LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.|
|bscookie||1 year||LinkedIn sets this cookie to store performed actions on the website.|
|li_sugr||3 months||LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.|
|VISITOR_INFO1_LIVE||5 months 27 days||YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface.|
|YSC||session||Youtube sets this cookie to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.|
|yt-remote-device-id||never||YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.|
|yt.innertube::nextId||never||YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.|
|yt.innertube::requests||never||YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.|
|_an_uid||7 days||No description available.|
|_gd1687981540406||session||Description is currently not available.|
|6suuid||1 year 1 month 4 days||No description available.|
|ifso_page_visits||1 year 1 month 4 days||No description available.|
|oribi_cookie_test||session||Description is currently not available.|
|oribili_user_guid||1 year||Description is currently not available.|