Some questions related to xCP 2.0

Hello Experts,

I have some questions regarding to xCP 2.0.

1. How can we validate the user input? How is that stuff supposed to be done?

2. Is xCP 2.0 OOTB activities such as link to folder etc. work on the top of DFS or DFC? Are they deployed to the docbase as BOF modules or something new?

3. What replaces SDT-s? What should we do if we want to share a list of variables across multiple workflows like in SDT's in 1.6?

4. Is there any way to move individual objects from one docbase to another?

Thanks in advance

Find more posts tagged with

Comments

PanfilovAB


1. How can we validate the user input? How is that stuff supposed to be done?

That's a challenge. If you would like to perform just a simple checks (like user should input numbers but not letters) you should write own function (http://www.emc.com/collateral/hardware/white-papers/h11306-xcelerated-composition-platform-ext-points-wp.pdf)

If you want to perform checks against docbase you should create stateless process, something like:

1. create label on the form (error_message for example), set it hidden if length(error_message) = 0

2. hide submit button in length(error_message) = 0

3. create a stateless process and bind form fields you would like to validate to process input variables, bind error_message field to output variable

4. implement some business logic in process and set output variable according to result

5. bind process to you form and trigger it when input changes


2. Is xCP 2.0 OOTB activities such as link to folder etc. work on the top of DFS or DFC? Are they deployed to the docbase as BOF modules or something new?

DFC, BOF.


3. What replaces SDT-s? What should we do if we want to share a list of variables across multiple workflows like in SDT's in 1.6?

I think EMC introduced STDs in BPM because BPM do not support repeating variables, now xCP supports repeating process variables and EMC developers think that there is no need to support SDTs (i think they have never thought that anyone shares SDTs between different processes)

Imran_Yusubov

Hello,

Thank you very much for your reply. I had just started to liking xCP 2.0. A lot of things were much better than xCP 1.6.

Stateless process templates, use of services instead of DQL and DFC and etc. But, why they touch to already working things and break them? STD's were better than process variables in many ways. In fact, I had been expecting features to work with objects rather than individual variables.

dnvhariprasad

"Business Objects" are the replacements for SDTs. However, we need to make sure to delete those objects if necessary.

Imran_Yusubov

Hello,

Business objects can't be bound to UI forms. That means duplication of the model across multiple workflows is a must. In this case, we have to copy the data from the UI to the process variables and then from process variables to the business object. However, this is very inefficient. If we decide to change the model later on, imagine how many things should be modified.