When a user receives a notification that a workflow action is available, the user clicks on the link in the email, which goes to the Actions tab, clicks on Edit on the Item Details tab, peform the requested action, clicks on Save, then go to the Workflow Actions tab, and click the arrow in the workflow so that the workflow advances. Is there a way to offer a "Save" or "Submit" button/flag (that would automatically advance) for the user so that there are fewer clicks?
Based on a value or status of a field, the ability to take an action based on changes to a field value.
Example, moving to the next step in the workflow. In the process to create a product name, the Person A asks Person B to create a name and get it approved by Legal. If Person B approves a product name, we would like the workflow to automatically advance to the next stage based on the "approved" status so that there are less clicks for the user and less chance of forgetting to advance the workflow on the Workflow Actions tab.
Product Line Code - which is the lowest level of child
Can we do a validation from a field in a Parent item details form to a child BOM?
The Pricing form has a field to display Product name and show some derived fields that are used in a pricing calculations. Can we ensure that somewhere down the chain of BOMs, that the same Product is added as a child?
The validation logic may possibly only be done on a workflow transition.
Form validations on the client side can save the user's time by pointing out errors in the form as they are entered or auto-populating values based on other values in another field.
An example is on a pricing form where there some data relationships that should not be broken and internal logic would be enabled based on values the user selects. If a user selects value 1 from picklist A, then picklist B would show a different set of values than if the user selected value 2.
Currently your outstanding tasks will show anything that you have the ability to change, this means that there is WAY too many items in the list then is relevant.
My solution would be to allow a script to run (on item creation although doesn’t really matter) that would take the information from a user pick list field (let’s call it Assigned to) and add that person to the additional owners of the item.
Then in the security settings do not give your users access to see items owned by others and hence leaving you with an outstanding items list that is relevant to you not your entire team.
I understand that I could just add them into the additional owners manually however this is extremely frustrating as there is nothing to prompt you to do so and is often forgotten, if it is a field then I can make it required.