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 cut down on mistakes.
Loading from the database.
- Use a dataloader at the top of the templates list of objects (on the Admin side)
- Based on who the user is, you can load their user data, their department data or their departments default address
- You can also allow them to select someone else in their department
Loading from Hashtags
- a Hashtag is unrelated to 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.
- There are two modes – hashtags saved per user and hashtags saved per storefront
- 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, 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, on any page will then also load ‘JFK’.
The second time John sees this field, it will show ‘JFK’ automatically. In fact 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’. For all users, all subsequent fields with the same hashtag will have ‘Sydney’ in them. UNTIL someone, anyone, changes it to ‘Madrid’.