Push Questions

[WRoeckelein]

Hi all,

I am investigating ways to use Mobile Documents with offline documents (ie the native clients) together with a custom mobile application which also provides offline functionality.

The mobile applications provides information to the user on tasks to be done and supports reporting on these tasks.

Together with the tasks I want to sync/push task specific documents to the user (eg a certain directoy in a company repository). When the task is finished, these documents should no longer be synced to the user. How can I accomplish this? Is there a (local/server) API to push/unpush to users?

While reporting the user might eg be prompted to add a photo to be taken with the camera of the mobile device. The photo should be stored in a specific directoy in a company repository. This should be initiated from the custom mobile application. Is there a local API to initiate document handover to the native client to sync the document to a certain folder?

Or are ideas like this beyond the current scope of Mobile Documents?

Regards,

Wolfgang

[Former Member]

Hi Wolfgang,

another way for an app to pass documents to the Mobile Docs app is via Open In or the Document Provider functionality.

The push flag currently can only be set on repository level via the AdminUI.

Best regards,

Peter

[WRoeckelein]

But with "Open In or the Document Provider functionality" I can''t handover a document to Mobile Document native client for storing and syncing?

[Former Member]

At first the documents are only stored (and uploaded) in the native client. The sync flag is not turned on automatically on those new documents, except the repository itself is marked as pushed or the parent folder has already a sync flag, then the sync flag get's inherited.

Best regards,

Peter

[WRoeckelein]

I don't need the sync flag on new documents from the client, since the folder will have push set already.

I need to set the push flag for folders via a API (from client or from server).

And I need to handover a document (not document name!) to the native client for storing inside a folder (so that it is later uploaded during syncing because that folder is currently marked for push and sync, if push does not include sync).

[Former Member]

Setting a push flag for folders via API is currently not possible.

Handing over a document (content & document name) to the MobileDocs App via the Open In.. or the Document Provider extension via "export" or "move" operations is possible.

[WRoeckelein]

ok, but Document Provider extension is iOS only, and you can't set a folder where the document should be stored but the users always chooses the folder.

So it seems I would have to upload the file my self though the CMIS API and if the destination folder is a push folder, the user will see the file in the native app as soon as the sync is finished.

Do I read this right, that I can set the push flag only on repo level and not on folder level in the UI?

[Former Member]

Yes correct, setting the push flag on folder level is currently not possible

[WRoeckelein]

This is a bit unfortunate for my use case.

Do you have an idea to circumvent this restriction somehow?

From the documentation https://help.hana.ondemand.com/help/frameset.htm?ed1c6732d4214c68846ab9813b9df943.html I learned the concept of a proxy bridge. Could the result of such a proxy bridge again be exposed via Mobile Documents? If I understand this correctly, I could calculate inside the proxy bridge which folders a user should currently see and expose only this specific folders (eg via filtering), right? I could then set the push flag on the exposed repo. Does the CMIS API and the push flag support user specific content of a repo? The mentioned documentation page says "Apache OpenCMIS project contains a bridge module". Could you direct me to this module (I only found the CMIS to JCR bridge which apparently was dropped with OpenCMIS 0.12.0)?

[Former Member]

When you set the permissions (acl) on the folders for the respective users so they only see what should be pushed to them, this could also be an option.

Which repository do you use?

Regarding the proxy bridge or the bridge module I will ping Florian Müller who is an expert on this topic, but you can expect an answer from him next week at the earliest.

[WRoeckelein]

We will use the HCP document service.

The acl can be set via API?

Problem is that users will not be able to see the documents when eg accessing via web interface, or?

So I would always need two (virtual) repos, one with push for offline access of assigned folders and one without for online access to everything.

[Former Member]

Yes you can write a custom client and call the applyAcl method.

Yes users would not be able to see the complete hierarchy and only see the pushed folders/documents when accessing via web interface.

Unfortunately there isn't a way to define such "virtual" repositories.

[WRoeckelein]

I was hoping to be able to define a "virtual" repo with the proxy bridge or the bridge module and filter the acl and publish the repo from the bridge with push enabled.

So in the original repo the users will see everything while eg using the web interface and when they access the "virtual" repo with the mobile client they will have the content assigned to them offline.

How is the sync of the pushed content triggered? Is there a UI element in the client for this (ie start a pull)? Does the sync happen when the app is started? Or is the server really "pushing" to the client?

[Former Member]

The sync is triggered when the app starts and can be triggered manually via pull-to-refresh in the synced section.

Let's see what Florian can tell about the proxy bridge or bridge module.

[WRoeckelein]

Hi Peter,

were you already successful getting some info from Florian Müller regarding  proxy bridge or bridge module?

Regards,

Wolfgang

[former_member186016]

Hi,

Integration between MobileDocs app and other Mobile apps can be achieved using custom url schema "mobiledlocs". http://help.sap.com/saphelp_mdocs10/helpdata/en/ae/dc3faf1acb4a2695e04a8693c74119/content.htm

Currently, open and select are supported by it.

Handing over documents to MobileDocs app is not there. But you can use CMIS APIs to uploaded them on server and then call open URL to open it in SMD client.

Regards, Ashwani Kr Sharma

[WRoeckelein]

Unfortunatly the custom scheme solves none of the challenges I mentioned, but yes, it helps in some aspects, but I knew this already, this is why I didn't mentioned this challenge (operning document in the native app from the custom mobile app)....