Custom Properties are customized fields you can add to Item, Contract, Make or any other sort of record in e-automate. If, for instance, you want to record the IP address of equipment, you can create a field on every Equipment Record to record it in. More to the point, CEO Juice uses these Custom Properties to identify records to check in alerts and to set some of the parameters for those alerts. You'll find documentation from us for each specific process indicating what the various Custom Properties are and how to fill them in to accomplish what you want to do. This article is meant as an introduction to what they are, how you find them, when you want to use them, and how you create them.
Where to find
Where to find Custom Properties on eAuto Records:
You find the Custom Properties for any record on tab named 'Properties' or 'Customproperties'.
If none present, then use the magnifying glass to select/click on from drop down:
If we have created Custom Properties for you based on process variables you are subscribed to, then all you need to do is go to the tab to edit Custom Property.
Equipment Record Sample:
Customer Record Sample:
We will add our Custom Properties to the configuration you already have set up for the record type. If you have none for the needed record type, then we will create a new one for you.
Once you see the Customproperties for the record, you can click on the Custom Property to edit as needed (just be sure to click OK to save!). CEO Juice Custom Properties always have names starting with the letter Z.
No Custom Property
No Custom Property Tabs
If you don't see the 'Properties' or 'Customproperties' tab on any records in eAuto, then go to Tools / Options / Misc. options and enable them by checking the box 'Enable custom properties':
Configs
Configuration Options:
Custom Properties are organized into Configurations (think of them as collections or sets of properties) assigned to a Group Type (i.e. equipment and contracts) . You can have more than one Configuration for a Group Type, but we HIGHLY recommend only having one configuration for each Group Type. Any given record in eAuto can only store the Custom Property values on ONE configuration. By having multiple, users will inevitably erase existing used Custom Property values by selecting a different configuration.
Here is an example of what NOT TO DO:
If a Configuration is already selected and you select another one, you are deleting ALL THE DATA on the first Configuration.
Best Practice is to only have ONE Configuration for each Group as shown below:
If you need to create a Configuration for a Group you don't already have:
Select 'New' in Lists & Codes / Configurations (custom properties):
1. Enter Name, Description, select Group you are creating new Configuration for
2. You must add at least one Custom Property to the Configuration
3. Be sure to select QuickAdd
4. Click OK to save
Custom Props
Custom Properties:
Individual Custom Properties are created as Attributes, and then assigned to one or more Configurations. Until the Attribute is Assigned to a Configuration, it's technically not called a Custom Property. Attributes are found via Tools / Lists & Codes / Attributes:
Double-click on an attribute to open and edit (Name, Description, some other details depending on the Data Type). Data Type means 'what sort of field is this?', for instance yes/no, text, date, etc. This cannot be changed after creation.
To create a new attribute, select 'New', be sure to give name, meaningful description, and data type:
Once you have your new Attribute, it must be added to the Configuration you've built it for; otherwise, you will not have the attribute/custom property available in the configuration drop down.
Go to List & Codes / Configuration (custom properties). You'll see all your existing Configurations. The column labeled 'Group' tells what Record type the Configuration is applied to. If there is already a Configuration for a given Record type (if, for instance, you already have a Configuration assigned o to Equipment Properties), then creating another one is almost ALWAYS a bad idea. Remember each record can only have one configuration active. If you create a new one and make it active on a record, you are by definition deleting the old one and all the information in it. This is why we will always piggyback our Attributes/Custom Properties onto your existing Configurations.
1. Double click on the Configuration you wish to add your new Attribute to
2. Use the 'Available attribute(s)' drop down to select your new attribute
3. If you want ALL records to have a 'Default value', then select that value. Remember this will apply to ALL records for this configuration type (Contract, Equipment, Employee, etc.) so be sure!
4. Select 'QuickAdd'
5. Be sure to click 'OK' to save
Now you will see this attribute available under Customproperties:
Missing Config
Missing Configurations:
If you are missing configuration in drop down on some records, you can bulk assign these in eAuto.
Go to Lists & Codes / Configurations (custom properties), then click once on the configuration group you need to update (i.e. contracts or customers), then click on 'Assign'.
From there, use the filters as shown in the screenshot below to assign/populate the configuration that is missing for your the records you've selected (i.e. Customer Records)
1. Filter by Configuration = blank and Active = Yes
2. Take note of warning from eAuto to make sure you understand what you are doing!
3. Click OK to update
eAuto gives you one last chance to change your mind! :)
Won't Save
Changes to Custom Property Won't Save
There is a bug in all eAuto versions where sometimes the change you've made to Custom Property on a record will not save (this is most often on Contract Records). You will notice the 'OK' button can't be clicked to save even after you've made an actual change in the Custom Property
The only workaround is to change something non-impacting on the record so the 'OK' button is now clickable, then change your Custom Property, and lastly click 'OK' to save both changes. Just remember to go back into the record to put back the non-impacting change to what is was originally set at.
0 Comments