Tracy,
The ideal long-term solution is to extend the security model to fully cover saved sets. This would allow edit privileges to be granted to users or groups (recommended). There are already enhancement requests submitted in this area, but you may want to open a Zendesk ticket making the request and specifying all of the use-cases you would like to see supported in this area to ensure they are all covered in the current requests, plus Steelcase would be added to the list of customers desiring this capability, giving it more "weight".
In the meantime, the ownership is defined on a record in the database. Transferring ownership to another user would simply require changing the created by field to that new owner. On one hand, the originating user would no longer be known but on the other hand, I think it is probably more important for the desired person to be able to modify the saved set than to retain this information.
A safe way for this to be addressed would be to define a repository that saved sets could be "registered". The user experience would be something like this:
1. The user creates a record in the Saved Set Registry repository.
2. They select the repository containing the saved set from a drop-down list of all repositories.
3. They select the saved set from the drop down list that only shows the saved sets for the selected repository.
4. They select the new owner for the saved set.
5. They save the record.
6. To transfer ownership, the user would submit the record to workflow. The workflow would alter the database table record, setting the created by field to the selected owner.
7. Subsequent transfers of ownership would merely require editing the record, selecting the owner, and sending it to the workflow.
Access to this registry repository can be managed through security as well as who can actually transfer ownership.
It wouldn't take much effort to create a Scheduled Export/Import combination that pre-populated this repository with all of the shared saved sets and their current owners.
If you think this would meet your needs, please let me know.
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 909-900-9179
------------------------------
Original Message:
Sent: 01-10-2022 09:59
From: Tracy Ishman
Subject: Business Users Editing Saved Sets Owned by Another
We recently discovered that a business user cannot edit a shared saved set created by another user. However, as an admin I am able to modify them. As a work around we have set up our business user to impersonate the owner of the saved set and he was able to edit it. This seems rather odd. What if the original owner of a saved set is no longer an EW user? The saved set would need to be maintained by administrators or be recreated by someone else. Is this working as designed or could we be missing something? Thanks!
------------------------------
Tracy Ishman | Senior Product Data Analyst
Steelcase, Inc | 2312255012
------------------------------