Mobile app and metadata card rules

Hi M-Files and community, 

We are now in process to test our use cases (different document types) on different platforms including mobile apps (Androids and IPhone). As you can imagine, many users are very excited that they would be able to create/edit document, move through workflow etc.

Unfortunately, I can see now that mobile app behaves slightly different as desktop application and that users actually can not create documents of specific document types.

The problem is related with metadata card rules that we use to hide specific metadata from users during "Created" workflow state (initial workflow state when metadata card is opened, initial state of the workflow). Some of metadata is mandatory and will be calculated automatically when user clicks on "Create" button so actually the value will be correctly filled out after creation.

In case of mobile apps, it seems that (even though) user selects prepared template (which is associated with workflow and first "Created" workflow step), the workflow and initial step is not selected! This causes that all metadata is shown to users (including those which will get calculated after click to "Create" button) and that user needs to provide them. We have actually disable the most of calculated properties so that user do not provide values but actually our VAF application prepare and calculate them. So actually through mobile app, users are not able to create document types at all!

So my questions:

  • Do metadata card rules apply to mobile/web at all and in which form?
  • How to enable those complex cases in mobile/web? (I assume in web it would not work either)

I see now this could be a big trouble for us as we have complex scenarios and need hide complexity from users.

How do you deal with this? Can someone elaborate more on options?

Thanks.

Dejan

Parents
  • I'm maybe a bit late on replying to this, but the use case sounds something that I would expect to work also in our mobile apps.

    In case of mobile apps, it seems that (even though) user selects prepared template (which is associated with workflow and first "Created" workflow step), the workflow and initial step is not selected!

    Could you explain a bit more what the above comment means? Basically what does the prepared template mean in this case?

    We are constantly making improvements for the metadata card configuration support on mobile apps. It would be very helpful if we could get sample configuration that we could use to see the issue ourselves.

Reply
  • I'm maybe a bit late on replying to this, but the use case sounds something that I would expect to work also in our mobile apps.

    In case of mobile apps, it seems that (even though) user selects prepared template (which is associated with workflow and first "Created" workflow step), the workflow and initial step is not selected!

    Could you explain a bit more what the above comment means? Basically what does the prepared template mean in this case?

    We are constantly making improvements for the metadata card configuration support on mobile apps. It would be very helpful if we could get sample configuration that we could use to see the issue ourselves.

Children
No Data