+3Hi, community!
I would like to let the users associate tickets only with the assets that are In Use or Reserved.
Any ideas how to do it? Something like not showing assets in other states in a table of assets available for association or automated error messages, when trying to associate an asset in another state? Business rule for this?
To restrict ticket association with assets to only those in "In Use" or "Reserved" states, design your user interface to display only eligible assets for selection. Implement backend logic to enforce this rule, preventing associations with assets in other states and triggering error messages as needed. Optionally, enforce this rule at the database level with constraints. Document the restriction clearly for users and provide training on its implementation and purpose. This approach ensures data integrity and reduces errors in ticket-to-asset associations.
+3Great advice, but how exactly should I do this? How to design the user interface to only display the assets in these states? How to configure the backend logic to restrict associations of assets in other states?
To restrict ticket association with assets to only those in "In Use" or "Reserved" states, design your user interface to display only eligible assets for selection. Implement backend logic to enforce this rule, preventing associations with assets in other states and triggering error messages as needed. Optionally, enforce this rule at the database level with constraints. Document the restriction clearly for users and provide training on its implementation and purpose. This approach ensures data integrity and reduces errors in ticket-to-asset associations.
+9Even with a workflow, the associated asset trigger, won’t let you check the status of the asset. Partly as they will be an array (potentially multiple assets associated), which Fresh doesn’t handle well.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
