How to resolve signatures not sync'd to the database?

General Q&A
1

Hi,

I got a scenario where the user is usually in a bad reception area or there is no connectivity. Is there a way in which we can make sure the signature has sync with the database to allow us to create reports. Sync rules are set up for the data model which consist of a field type of a signature.

There 2 signature fields for the data model, one doesn’t sync while the other does.

regards

2

Hello @sisa-zaza

Could you email support@journeyapps.com with a link to the app and associated code so that we can further investigate this issue? We can post any findings here to help the community with syncing signatures.

Thank You,
Travis

3

@sisa-zaza Before logging a support ticket, you may also reference this post to implement a webhook that triggers the report task once the attachment has uploaded.

For this implementation, the signature fields would have to be on the same model that triggers webhook for the report task.

Additionally, here are three ways to check that attachments are synced to the OnlineDB:

// Option 1
if (job.photo.state === 'uploaded') {
   var original = job.photo.urls.original;
}

// Option 2
if (job.photo.present()) {
   var original = job.photo.url();
}

// Option 3
if (job.photo.uploaded()) {
   var original = job.photo.url();
}
4

Hi @travisroach ,

job.photo will cause an error as the photo is null. I tried the above but doesnt work. I did log a support ticket though.

I got two fields in one data-model that store user_one_signature and user_two_signature. They both get signed on the same screen but for some objects/records, user_two_signature is always present.

I have asked the support team to add the solution to this community entry…

5

Hi @sisa-zaza

If job.photo is null then it means the photo was not captured at all, it does not mean that the photo hasn’t been synched yet. If the photo was captured but not synched then job.photo will not be null, but job.photo.present() will be false.

Is your problem that one or both of the signatures are not captured at all, or are they captured but not synched at the time when you try to create the report?

6

Hi @tielman

The problem is that both signatures are captured but one of the signature is not synced at all.
To continue with the workflow, both signatures need to be captured. If one signature is missing then the user is blocked from continuing with the workflow.

7

Ok. That sounds like a bug then. @travisroach ’s instincts were right, please contact support providing us with one or two examples (links to objects in the backend) where one signature is present but the other not. Also provide a link to the codebase and the full path of the view in question where the signatures are captured.

8

We are reviewing an existing support ticket logged by Sisa. Thanks @tielman

1 Like