Change Fields

What exactly is a change field and what in the world does one of these fields accomplish? Well, the title of the field kind of says it all. Change fields allow for change!

 

Simply stated, a Change Field creates a record of changes that occur during an action. For instance, lets say you sell an asset. A change field automatically updates the status of that asset to Sold. (We told you it was simple!)

 

 

Create a change field

First, it helps to know how to actually create a change field. I mean, it's kind of difficult to use one if you haven't yet created one, so let's delve into first things first.

 

To create a new Change Field:

1. Scroll down to the Change Fields section of an action, and then click New Change Field.

 




NOTES: Most of the selections within this setup window will be made using drop-down menus.

Your options may differ from ours, depending on your Change type selection.

 



2.Select the Group in which your change will occur.
3.Select the Field in which your change will occur.
4. Determine the type of change you would like to occur within the Change type field, along with what you would like your field to change to within the Change field to text field. You will need to do the same for the return fields (Change type on return and Change field on return to).

 

And...we've created a nifty table that should help you to choose the change type that best suits your need.

 

Change Type Table

Change Type Change Result
Set Value This option is the default option, allowing you to choose what you wish your field to change to. (For instance, allowing you to set the status value to Sold.)
Prompt User This option prompts and requires the user starting the action to enter or choose a value for the field.
Update if value is blank This is a Yes/No setting next to the change type, not a change type itself. Select Yes to update the field even when the value being applied is blank. Select No to keep the existing value when the new value is blank.
Update with value from Action field Use this when the new value comes from a field the user fills in while running the action. The field you are changing takes the value of a matching open field. (For instance, an open Location field in a check out action can be copied into the Assigned to field on the record.) This works for group list fields too, such as an open field where the user picks an employee.
Delete Value This option will delete the value of your chosen change field. (For instance, you may want to return an asset and then delete the data of the assigned to field, enabling it to be replaced with the next person the asset is checked out to.)
No change Selecting this option means that nothing will happen to this field. This field is typically used for the change field on return to.
Update with Value from Group Field Copies a value stored on the record the action is run on into the field you are changing. (For instance, copying the Location stored on the record the action is run on into a linked record.) This option only appears when that group has a field of the same type as the field you are changing. It does not read open fields, so to use a value the user chooses while running the action, such as an employee, use Update with value from Action field instead.

 

5. Select Yes or No for the If a user does not have access to write to this field, should this field be updated field. It is recommended that you select Yes for this option so that all users have the ability to update specific fields (see below). See Custom Permissions for more information on security permissions.

Selecting Yes will allow the user to update the field, even if they do not have the permissions to do so. (For instance, the user does not have the permissions to manually edit fields within a record. Selecting Yes will allow the user to still be able to complete the action, updating the fields on the backend.)

Selecting No will only allow the user the ability update the field depending on their permissions. (For instance, the user would not be able to use actions to update certain fields such as Status and Assigned to.)

 

6. Click Save and Close. You have just created a change field. Need more than one? No problem. Just rinse and repeat!

 

Change fields in a different group

An action can change fields in a different group than the one it runs on, as long as the two groups are linked by a group list field. (For instance, an action on a parent group can update the records in a related group.) Select the other group in Group, and then fill in Source of relation.

Source of relation tells Asset Panda how to find the records to update. Select the group list field that links the two groups, whether it sits on the group the action runs on or on the group you are changing. Without it, the action cannot reliably find the linked records, and their fields may not change.

Example: a Check Out action on one group should also set Checked Out To on the linked records in another group, using the employee the user picks when running the action.

1. Add an open field to the action where the user picks the employee (for instance, a group list field pulling from your Employees group).
2. Add a change field. Set Group to the linked group and Field to Checked Out To.
3. Fill in Source of relation with the group list field that links the two groups.
4. Set Change type to Update with value from Action field, and set Change field to to the employee open field from step 1.

Use Update with value from Action field any time the value is chosen in the action, even when that field is a group list. Update with Value from Group Field is only for copying a value already stored on the record the action runs on.

Related Topics

Action Fields

Closed Fields

Open Fields