Unique Workbasket Names in FCM
While implementing FCM, is it mandatory to have unique workbasket names across all applications that are part of Federation ? If not, how does operator know which workbasket to pull work from when workbaskets from two different applications have identical names ?
Can an operator drag and drop work from Remote workbasket into local workbasket and vice versa ?
Accepted Solution
Pegasystems Inc.
US
I don't think there is a mandatory requirement for unique workbasket names, however you are right to consider the end user confusion such a design would entail. As a best practice I would suggest you try to have different work basket names in this situation. Some customization may be required to the out of the box implementation to disambiguate the workbaskets if you use the same names.
Pegasystems Inc.
US
We don't have any federated drag and drop capabilities, however you could take a look at how pyDashboard7 does it for the local system, if you wanted to customize the out of the box Federated work list towards a drag and drop solution.
Bank of Nova Scotia
CA
Thanks Peter for a quick response. That's what I thought that unique name might not be a requirement for FCM but would confuse user. However, in situations where we want to enable existing applications for FCM and if they happen to use same workbasket names, then it might be very difficult to change workbasket names if application logic is dependent on these names.