What happens when I save with multiple records open? Use a Save button for server-side saving. Make it easy for users to view and revert to previous versions. If a builder autosaves (and creates auto-versions for each save), batch any changes into a new version.If your builder does so, let users clone or copy objects with a Save As command. Alert the user to any errors blocking activation/publication. When a save also triggers activation/publication, allow the file to be saved without push.(See Validation for more information on messaging.) When a builder allows manual saving, users should be allowed to save even when their work contains errors.Use a Save button to initiate a server-side save of the entire object.When and how can I save my builder objects? If saving does activate/publish a file or execute a process, explicitly call this out. Note that saving does not equal approval to push an object for activation or publication these are two separate actions. Saving is a server-side snapshot of an object and its state. Some builders also let users activate, run, or publish. When working in a builder, users tend to save changes often.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |