{{UnderConstructionStart}}
== Use Case Functionalities Entry Points ==
To display various data in the Admin Tool, we have the following Entry Points with Use Cases under them:
<tabs>
<tab Name="00 - All Important">
Under Entry Point 00 - All Important are the following Use Cases:
* All Icons: Displays all icons that have already been created / set up.”
* Job Runs: Displays all jobs that have been initialized for all turnaround projects.
* Turnaround Project: Shows all Turnaround Projects in the database. It is important for the execution of jobs.
</tab>
<tab Name="01 - All Other">
For the 01 - All Other Entry Point, its Use Cases show all Data, regardless of whether instances are Templates or belong to a Project or not. Under Entry Point 01 - All Other, there are the following Use Cases:
* Activity Codes
* Commissioning Codes
* Commissioning Packages
* Commissioning Tasks
* Companies
* Daily HSE
* Daily Meetings
* Equipment Groups
* Equipment Types
* Equipment’s
* Execution Documents
* Functional Locations
* Functionalities
* Material
* Media
* Notifications
* Operations
* Plants
* Plot Plans
* Predefined Filters
* Predefined Views
* Preparation Documents
* Punchpoint Attachments
* Punchpoints
* Quick Access Items
* Reports
* Scope Change attachments
* Scope Changes
* Subsystems
* Systems
* Timesheets
* Users
* Workorders
* Zones
</tab>
<tab Name="02 - Templates">
The Use Cases under this entry point are for displaying data that is only marked as a template. By default, there are already pre-made Use Cases for displaying template data, which are the following:
* Activity Codes
* Commissioning Codes
* Equipment Group
* Equipment Type
* Functionalities
* Users
</tab>
<tab Name="Turnaround Project">
===Project-specific Entry Points===
These entry points display data that belongs to the respective project. For example, if the TurnaroundProjectCreationJob is executed for a Turnaround Project, there will be a new Entry Point created for this Turnaround Project. All Use Cases under such an entry point only display instances belonging to this specific project. There is also a difference between the TA Project Entry Points and the 01 - All Other, in that the TA Project Entry Point has one more use case, the Turnaround Project Use Case. This use case displays only the Turnaround Project in which it has been opened.
</tab>
</tabs>
== Use Cases ==
<tab Name="All Icons">
Under this use case, it is possible to create icons, which can then be assigned to Contractors / Companies.
[[File:MatapIcons.png]]
To be able to upload a photo, the name and description properties must be filled out and press “Enter”. Then a double click has to be made on the instances "Icon" property (without a sign on the left side) and then on the button with the three dots. After that a Windows Explorer will open and a selection can be made for the desired image. When the selection is uploaded the icon field will be filled automatically and the last step is to save everything. The icon is now successfully created and could now be assigned to a contractor/company.
</tab>
<tab Name="Functionalities">
Under this use case, you can view and edit the root items (tiles) that are delivered to the clients.
* G1 General WallpaperWrite Group (UWP)
* G30 General ReadProject Group (Xamarin).
</tab>
== Whitelist ==
We can configure, with the help of the whitelist, which columns we want to have/see for each use case in the Bulk Editor. This helps us to present our data more clearly. For the Use Cases provided via the system definitions, we already have defined Whitelists that can be adapted when needed.
Now we come to the configuration of the whitelist for a use case:
1. Open your UBIK.Studio.
2. Navigate to the following point: System => System.Matap => System.Matap.AdminTool => USE_CASE_ADMIN_TOOL_QUERY.
3. Open the USE_CASE_ADMIN_TOOL_QUERY in the Bulk Editor.
4. Open the use case whose columns you want to change in the Relation Editor.
5. Drag and drop the Meta Property which you want to have shown into the REL_COLUMN_WHITELIST Section and the configuration is done.
== MP_PRELOAD ==
There is also the possibility to preload properties, and this can be set with “MP_PRELOAD”. Just check this, and the property where the “MP_PRELOAD” was set will be preloaded. This can be set individually for each property.
<br/>
{{UnderConstructionEnd}}
[[Category:Templates|Entry Points & Use Cases]]
[[Category:MaTaP|Entry Points & Use Cases]]
[[Category:Templates|Entry Points & Use Cases]]