Loading data into templates.
When a customer clicks on an editable product, you might want their data to load into the template automatically. This makes things faster and simpler for the customer and can reduce mistakes.
Loading from the database.
Use a data loader at the top of the templates list of objects (on the Admin side)
Map the default content of various fields to the user, department or address table
Data will then be automatically loaded, and the customer can also select someone elses data (restrictions can apply)
Loading from Hashtags
A Hashtag is unrelated to the orthodox database (users, departments etc.)
If you nominate a hashtag (simply creating a new one like ‘Airport’), whatever the user writes in, will be stored on that hashtag.
Any field with the same hashtag will automatically load the same data.
Hashtags can be saved in two modes
Per user means that whatever John writes for a field will not be shown to Susan.
Per storefront means that when John writes something in, that becomes the new content for the hashtag for all users, until the next user changes it.
Example 1 = User-based = The first time John sees this field and can edit this field on any product, the Airport hashtag will be empty. He can fill in ‘JFK’. Any other field on that product or any page will also load ‘JFK’.
The second time John sees this field, it will show ‘JFK’ automatically. It will always show JFK until John changes it.
Because this is a User based hashtag, when Susan sees the field for the first time, she will see it as empty and can write in ‘Paris CDG’.
Example 2 = Storefront based = The first time anyone in the Storefront sees this field, it will be empty. John or Susan can write ‘Sydney’. Then, for all users, all subsequent fields with the same hashtag will have ‘Sydney’ in them. UNTIL someone, anyone, changes it to ‘Madrid’ or something else.