Question

DWA : Best practice to send multiple assignments using DWA

I have a requirement where i need to get sign off from external users .So would like to use DWA.

So what is the best practice is here.

Using spit-for-each and creating three external assignments or creating sub cases for each assignment.

Thanks in advance.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
August 31, 2017 - 10:37am

There is no best practice as it depends on the requirements and specific use case. A spin-off creates assignments on the same case therefore locking may be an issue if they are processed at the same time. This is unlikely but may periodically occur. Subcases (with locking independent of the parent case) would avoid this issue. This is at the expense of using extra database and additional processing to deal with the subcases and data propagation (if required).

Comments

Keep up to date on this post and subscribe to comments

Pega
August 31, 2017 - 10:37am

There is no best practice as it depends on the requirements and specific use case. A spin-off creates assignments on the same case therefore locking may be an issue if they are processed at the same time. This is unlikely but may periodically occur. Subcases (with locking independent of the parent case) would avoid this issue. This is at the expense of using extra database and additional processing to deal with the subcases and data propagation (if required).

Pega
September 1, 2017 - 1:42am
Response to ADAIJ

I don't think locking will be an issue in case of external assignments.

As you mentioned it depends on how business wants to handle.

September 11, 2017 - 1:51pm

To send multiple assignments using DWA I would prefer to create sub cases to avoid locking issues because it is an external user.The application should be designed to minimize the error messages for the external user.