15 03 2015
Overview Of Use Case Wizards
After creating an Entity like a “Book” the user can setup its corresponding Use Cases with the help of Use Case Wizards in just five minutes. However, if your Entity has interactions (dynamic) or relations (static) with any other entity, it may take a bit longer to establish – in any case, the wizards will make it much easier to achieve such goals.
Apps First contain four different Use Case Wizards are there. These wizards enable the user to fill the app with rich functionality related to the created entity with less effort.
1. Wizard for Basic Use Cases
This wizard is used to create basic Use Cases required for the selected entity. All the common use cases can be created using this wizard.
2. Wizard for Standard Use Cases
In addition to the basic Use Case, you can add several other cool features and advanced functionality to your Entity by using Standard Use Case Wizard. For example, you can add advanced attributes like “Notes”, “Review Notes”, “Documents” and “Authors” etc. Some of them are out-of-the-box features, which you can add in just seconds. In the above example, Notes, Review Notes and Documents are already available functions in the system and you are only integrating them with the ‘Books’ entity. However, Authors may be a new Entity which you have to create separately. Now you also know that an entity and Use Cases for Authors can be developed in minutes using these cool wizards of Apps First.
3. Wizard for Master Detail Use cases
If the entity created by the user has a relationship with already created entity,then the user can use Master Detail Use case wizard for creating the relation. For example the entity Books has a relationship with the entity Author, Here the entity Author will be the Master entity and the Book will be the Detail entity. So here the user can use this wizard for creating this relation.
4. Wizard for Master Detail Master Use cases
If an entity created has relationship between two already created entities then user has to use master detail master Use Case. For example entity employee qualification has a relation with employee entity as well as qualification entity. For creating this relation user can use this wizard. Here the employee entity is one master and qualification entity is another master. The employee qualification entity is the detail entity.