The number of visitors are stable since the relaunch of crazyapple.com.
318 unique page visitors from 32 countries with ar average visit duration of more than 3:20 Minutes.
The users with the longest visit duration came from Brazil (00:20:28), Switzerland (00:12:03), Hong Kong (00:09:20), Russia (00:06:36) and Germany (00:05:11).
And – of course – the e20-120 exam questions was the most clicked content.
Table: TopTen Page Visitors
Land/Gebiet
Visitors
Pages/Visitors
Germany
75
3,26
United States
63
1,58
India
49
2,47
France
41
3,36
Australia
18
1,17
United Kingdom
15
3,4
Hong Kong
15
9,8
Canada
14
2,25
Philippines
14
1,25
Turkey
13
1
317
2,65
If you have any questions or good ideas please leave a comment below this article.
You can use external systems or technologies using a variety of transmission protocols (e.g. SMTP, FTP or Java Messaging Services).
Correlation identifiers are similar to the r_object_id attribute and implemented as a 32 character string containing hexadecimal letters.
The Process Integrator handel two types of communication:
Synchronous – a request is sent and the response is immediately received (no real time, negligible delay)
Asynchronous a request is sent, but the answer might never be received or will be received at a later time
Correlation ID vs. Correlation Set
Correlation ID explained using the example of the email activity.
The correcation idenifier can be embedded in the subject header of an outgoing email. The email inbound activity parsed the Subject header and extract the correlaction identifier.
Positve:easy and fast to use Negative:Subject header of the incomming email could only contain the correlation identifier and no other additional text. If the matching process instance is not found a correlation error occurs:
ERROR com.documentum.bps.email.inbound.runtime.EmailTask - Could not process the message for 'Process - simple_email_action Activity - Email Inbound - Step'
Listener: 'Process - simple_email_action Activity - Email Inbound - Step'
Workflow: 'null' - 'null'
Workitem: 'null'
Process: 'simple_email_action' - '4bde75d18000853d'
Activity: 'Email Inbound - Step' - '4cde75d1800082b2' - Activity Template: 'Email Inbound - Step'
com.documentum.bps.inbound.WorkflowNotAvailableException: Workflow not found
Correlation Set
The correlation set can be defined in the Process Properties in the Advanced tab. The set can contain process variables and structured data taypes. Process Parameters or Package informations are not allowed and available.
The Process integrator will always attempt to use a correlation identifier (not correlation set). If the ID is not available the preconfigured correlation set will be used.
Remember: a correltion identifier in the email subject is not an effective way to match the correct process instance.
Best practice is to create a additional set of Process variables. One of these variables is named message_ID or transaction_ID and contains the internal identifier of the outbound SMTP activity. In the email inbound step the email attribute Reference will be mapped to the Correlation Set attribute transaction_ID (ref. screenshot).
Here you can find a short overview of two of the automation features that documentum offers. It helps you keep in mind the most important differences. In combination with aliases they even can be transferred from one repository to another. For further information please refer to the corresponding documentation.
Lifecycle
Workflow
A lifecycle is what happens to an object.
A workflow is what people do to an object.
A lifecycle is a set of linearly connected states.
A workflow is a network of activities.
artifact in a Documentum project, to be installed or uninstalled
not implemented as a project. Using Project builder WFs can be changed using a checkin / checkout function.
Documentum Composer
Workflow manager and Process Builder, but not in Documentum Composer.
instance of dm_policy
instance of dm_process
without run-time instances
with run-time instances (When a user starts a workflow, the server uses the definition in the dm_process object to
create a runtime instance of the workflow. Runtime instances of a workflow are stored
in dm_workflow objects for the duration of the workflow. )
definition states: draft, validated, installed (states that have absolutely nothing to do with the states in the LC which are stored in attributes i_state_no, state_* and others in dm_policy object)