Hi,
Right now, in a custom action when you want to update several fields you need one separate step for each of the fields. If, for instance, you want to update a couple of fields in all the children of a task, you need a couple of steps that will iterate twice through the list of sub items. I think this is pretty inefficient. Ideally, same as when you create a new entity, when updating fields you should have an option to add as many fields as needed. I think this would improve performance and would be an overall gain for both Clarizen and the users.
Thanks for taking this into consideration.
Please sign in to leave a comment.
Fernando,
Excellent point but I believe there is a way to do this by modifying the logic in the Custom Action but I am not certain how off the top of my head and would need to research this. In order for the proper group of Engineers to see and respond to this post, would you please repost this message in the Customization section. I will also look into it and see about getting you a quick response on how to go about this.
Sincerely,
Boris
Fernando,
Actually, can you provide more information? If you can specify how your Custom Action is created with screen captures of all settings showing the Custom Action, It will help me better understand what you are doing within the action and what you want to make more efficient.
Are you referring to the fact that the Actions are separate and you have to define separate steps for each field update? I am not certain how you have it setup but if you have the Custom Action at the Task Item Type, then it will run against all Task, this includes sub-Tasks based on your criteria logic. If you have 2 actions, each will do this separately.
As for the updating fields upon adding a new entity, what do you mean here? do you want to populate existing fields with information when creating a Task or Project, etc? This can currently be done in different ways, whether by showing the fields in the New Object (i.e. Project) Layout to expose those fields and allow you to update them initially or via Workflow that runs and populates the fields on work items when they are created.
Sincerely,
Boris
Hi Boris,
I have attached a couple of screenshots. The first one ("single_action_multiple_fields_on_create") is how you can create a task setting several fields at a time. The second one ("multiple_actions_multiple_fields_on_update") is about how you update the same fields and as you can see you have to do it in several actions. I think it would be more efficient to do it in just one action same as when you create a task.
The sub items comment was just to illustrate that it is even more inefficient if you have to update several fields on related items using "Run On". I attached one more screenshot ("multiple_actions_multiple_fields_on_update_on_children") to show that. If we could do it in one single action it would be way faster.
I hope it's clear now.
Thanks.
Fernando,
Thank you for the detailed information. I will present this to our Product team and let you know what they say.
Sincerely,
Boris
Fernando,
Thank you for submitting this request. Your change request was logged. ID: CR-232759.
Sincerely,
Boris
More than 3 years old, this is still a critical idea. An "Update Object" rather than "Update Field" option should be available. The interface would be identical to "New Object", where you can select one or more fields to be updated simultaneously. It would not only be far more efficient,. it would eliminate some update collisions.