Best Practices for participants?
![]() I'm looking for best practices around Participants, specifically those that are for the same operation. For example, we have a participant for workItemSave that will generate an Approval if needed based on a set of criteria for a User Story work item. We are also going to look at doing something similar to generate Verification type approval records for Defect work items. Is it the best practice to put both of these in a single participant? Is it the best practice to have 1 participant per operation (workItemSave) and have everything you would ever want to do within the save operation in a single one? One per work item type? On per logical "use case"? Susan |
2 answers
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.