Solution accelerators: Form design guidelines and examples
The following is a collection of Winshuttle Master Data Solution Accelerators and design patterns for creating Master Data forms and workflow solutions.
Solution Accelerators are based upon the idea of Design Patterns, and serve as guidelines for creating and implementing forms and workflow solutions for Master Data. These Solution Accelerators were created given the functionality of Winshuttle products and the environments in which they were used at the time of their creation.
With Solution Accelerators and design patterns you can streamline the design and implementation phase of Winshuttle forms and workflow solutions for Master Data. (Note that not all guidelines will apply to your particular environment.)
Who is this for?
This information is generally intended for existing Winshuttle users and assumes general familiarity with Winshuttle products, Microsoft SharePoint, and (where applicable) Microsoft InfoPath. See More Help if you would like additional information about Winshuttle products, training, and more.
|Solution Accelerator||Description||Applies to|
It’s usually recommended to use a different view of a form for each role in a work flow based upon the responsibility each role has for the data in the form. Each user will only see what they need.
When creating or changing master data records, a live SAP search can be useful for two reasons:
Auto-filling the fields from an existing record requires less time than filling out an entirely new form. This is recommended for the following cases:
Where applicable, you can set certain fields to default values based upon other data (different selections) in the form to create a "smart" form. This saves the user's time, and allows only possible combinations to be selected.
Adding validation where mistakes in data entry might occur reduces the time needed to complete a form. These validations can be SAP validation, business rules, and/or external/3rd party validations.
A revision loop can reduce the time required to complete a form when you have a workflow that involves multiple roles. It allows a user to resend an existing form back through a process (or sub-process) if a mistake is made, and thus eliminate the need to start an entire form over.
Fields can be restricted to "read only" so users can view but not edit the information in the form.
Naming conventions make it easier to develop, track, and manage forms.
Material Master records typically require multiple views and/or extensions (e.g. plant, sales org, etc.), which in turn requires multiple scripts to enter all necessary data into SAP. It is a dynamic, complex process. By creating multiple scripts and using conditional linking to chain them together, you can create, extend and/or change multiple materials in one spreadsheet with a single button.
If address errors occur at data entry, using an external validation system to verify postal codes and/or a complete address (e.g. Street, ST or St.) is recommended.
Often master data forms require multiple functions within a single form--search, create, and change, for example. This may result in the same fields being repeated in each script for the same Master record.
This design pattern describes options for simplifying a form where fields may be repeated in multiple scripts and what to avoid.
Use a SharePoint list to maintain Excel drop-downs for easy, centralized maintenance of multiple files with multiple users. Auto-schedule updates to your SharePoint list from SAP with Winshuttle Query.
Use a single spreadsheet to manage SAP condition records for better efficiency. For this Solution Accelerator, we will show how you can use one master spreadsheet to extract existing pricing and update new pricing for all condition records to simplify the user experience.