Difference between revisions of "HowTo:Make an Object appear on the Mobile Client"
(→{{UBIK}} SmartStudio) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Publishing an object's data, including its children, properties and documents, requires to configure the [[Application Context Management]] (ACM). | + | Publishing an object's data via the {{UBIK}} web services, potentially including its children, properties and documents, requires to configure the [[Application Context Management]] (ACM). |
| − | + | ||
=== {{UBIK}} Studio === | === {{UBIK}} Studio === | ||
| Line 13: | Line 12: | ||
# Restart the {{UBIK}} Content web service | # Restart the {{UBIK}} Content web service | ||
| − | + | ||
| − | + | ||
| − | + | ||
=== {{UBIK}} SmartStudio === | === {{UBIK}} SmartStudio === | ||
| Line 22: | Line 19: | ||
This can be achieved using the Application Graph, connecting a Scope for the object to be shown either as a root scope to the Application Context (requiring a root object Query delivering the object in question), or as a child to another Scope (requiring a parent object to be available). In both cases, a Scope modelling the look & feel for objects of that type needs to be provided. If the object should be farther down the hierarchy (not a root object), also a connection between the Scopes for the object and its parent object must be provided as well. | This can be achieved using the Application Graph, connecting a Scope for the object to be shown either as a root scope to the Application Context (requiring a root object Query delivering the object in question), or as a child to another Scope (requiring a parent object to be available). In both cases, a Scope modelling the look & feel for objects of that type needs to be provided. If the object should be farther down the hierarchy (not a root object), also a connection between the Scopes for the object and its parent object must be provided as well. | ||
| + | # Set up web services. | ||
# Configure a view hierarchy in the Application Graph. | # Configure a view hierarchy in the Application Graph. | ||
| + | ## Drop an application and context on the graph. | ||
| + | ## Drop scopes on the graph describing the look & feel of the objects on the mobile client. | ||
| + | ## Connect the scopes to the context or each other using drag & drop to establish a navigation hierarchy. | ||
# Save the Application Graph to the {{UBIK}} Environment. | # Save the Application Graph to the {{UBIK}} Environment. | ||
# Publish the meta definitions to the {{UBIK}} web services. | # Publish the meta definitions to the {{UBIK}} web services. | ||
| − | # Restart the {{UBIK}} web | + | # Restart the {{UBIK}} Content web service. |
| + | |||
| + | |||
| + | === Troubleshooting === | ||
| − | + | # Check whether the meta definitions were published. | |
| − | + | # Check whether the web service was restarted. | |
| − | + | # Check whether there is a scope for the object in question. | |
| + | # Check the visibility of the properties in case they are missing. | ||
| + | # Check whether the object is either a root object, delivered by query or connected to its parent object correctly (scope connection in ACM and reference or relation on content). | ||
| + | # Check for errors displayed on the client. | ||
| + | # Check for errors logged by the web service. | ||
=== See also === | === See also === | ||
Latest revision as of 15:40, 20 November 2019
Publishing an object's data via the UBIK® web services, potentially including its children, properties and documents, requires to configure the Application Context Management (ACM).
UBIK® Studio
- Set up web services
- Create a new Application
- Create a new Context
- Create a new MetaClassScope or Create a new QueryScope
- Create a new View
- Create a new ViewItem
- Release the meta definitions
- Restart the UBIK® Content web service
UBIK® SmartStudio
Objects can be shown on the mobile client by configuring a compatible view hierarchy using SmartStudio. This can be achieved using the Application Graph, connecting a Scope for the object to be shown either as a root scope to the Application Context (requiring a root object Query delivering the object in question), or as a child to another Scope (requiring a parent object to be available). In both cases, a Scope modelling the look & feel for objects of that type needs to be provided. If the object should be farther down the hierarchy (not a root object), also a connection between the Scopes for the object and its parent object must be provided as well.
- Set up web services.
- Configure a view hierarchy in the Application Graph.
- Drop an application and context on the graph.
- Drop scopes on the graph describing the look & feel of the objects on the mobile client.
- Connect the scopes to the context or each other using drag & drop to establish a navigation hierarchy.
- Save the Application Graph to the UBIK® Environment.
- Publish the meta definitions to the UBIK® web services.
- Restart the UBIK® Content web service.
Troubleshooting
- Check whether the meta definitions were published.
- Check whether the web service was restarted.
- Check whether there is a scope for the object in question.
- Check the visibility of the properties in case they are missing.
- Check whether the object is either a root object, delivered by query or connected to its parent object correctly (scope connection in ACM and reference or relation on content).
- Check for errors displayed on the client.
- Check for errors logged by the web service.
