Last modified on 30 December 2013, at 14:09

Create a new Document (UBIK Android)

Revision as of 14:09, 30 December 2013 by NWE (Talk | contribs)


This article describes how to create UBIK® Document objects on the UBIK Android client.

Prerequisites

Since UBIK® objects on the Android client are arranged in a hierarchy, every object (except root and infrastructure objects) have parents and, eventually, children. Therefore, in order to create any kind of object on the UBIK® Android client, a legitimate parent is needed.

It is necessary to configure this possibility in the Application Context Management (ACM) using the UBIK Studio. You can find more information on publishing content on the mobile application in this How-To: Make an Object appear on the Mobile Client.

More precisely, a Meta Class configured in the ACM can have so-called "possible child classes". If one of those is a document Meta Class, you can create such a document object as a child of an object which has the respective parent Meta Class. A Meta Class is a document, when it has a document classification.

For more information on documents on the Android client, please refer to Documents (UBIK Android).

Navigation to the desired parent object

As described above, a new object can only be created "under" a legitimate parent object. Hence, the first step to the creation of a new object on the UBIK® client is to browse the Content Browser and navigate to the desired parent object.

On the following, first two screenshots, you can see the Content Browser icon on the start screen and what the object list looks like.

For all successive levels (once an object is selected), the Content Browser displays not only the three tabs "Children", "Properties" and "Documents", but also context-sensitive actions. Browse down the hierarchy until you reach the parent object you want to attach a document to.

Using the Context Action for Content Creation

As mentioned, the Content Browser provides context sensitive actions for a currently viewed object. On the following screenshot, you can see the overflow menu button (three dots) which is displayed when the context action icons don't fit on the screen. In this case a click on it opens a dialog containing all the available context actions.

If you are using a tablet or the portrait orientation, the respective actions might be displayed as icons next to the tab view as well.

However, to create a new content object, you can either choose an object type (its Meta Class) or directly take a picture using the camera. If there are multiple "picture Meta Classes", you will be asked to choose one, though.

Choosing a File

Now, the actual file the document object refers to is adressed.

If the Meta Class you chose in the previous step was a non-document meta class, this step is skipped. Also, if you chose to take a picture, this step is replaced by the camera activity to create the file by taking a picture.

Normally you get to choose a file though, and this is done using any third-party file browser already installed on the device. If multiple file browsers are installed, you have to select one, as the following screenshot shows.

Depending on the file browser, the process of choosing a file might differ, so there is no screenshot fo this (but I think you'll succeed nonetheless).

Finishing the Creation

After a file was selected, you can edit the properties of the newly created object or even cancel the creation. If everything is as desired, you can finish the content creation with a click on the "OK" button.

The newly created content should now be visible as a new document object in the thumbnail grid view (or if it wasn't a document, in the children list).

Committing the new Document

Now it just has to be committed to the server and it will come back with a thumbnail and a description (if the ACM and the customizing is configured that way). Congratulations!