You can store almost any type of data you want in any field except for the two Date fields – the Start Date/End Date fields will only accept Date/Time formatted data due to the field’s Data Type.
The Date fields will automatically contain the Date/Time the state was recorded if you keep the Action and Rule configuration as shown, so you don’t need to explicitly set them anywhere else.
The Name field is used as an identifier. This way, when Reporting, we filter records by Name so as not to confuse TimeClock with DrawerOpen. Maintain this consistency at all times; you could use ButtonPress or DrawerKick or any other name – you will use the Name to filter your Reports.
The State Name (Group) and State fields can also store whatever you want and in your case, they are fairly arbitrary. You could even put the User’s Name there if you wanted, but it would be more useful to store the button name as the State and the User’s Name as the State Name (Group).
The CustomData field is for holding anything you want that is not related to States or Entities.
When you log into the file, you will instead insert the Update Entity State Action and set the State to whatever you want. You could set the State to the name of the button or action that caused the cash drawer to open and the State Name to the User’s Name. Of course, set the Entity to the name of the Entity that you defined for the purpose of logging.
Then, you create a Rule for Entity State Updated and put the Log Entity State Action in it. Restrict the Rule to only operate on the Entity you defined for the purpose of this log.
