Policy Automation for B2C Service

Get Involved. Join the Conversation.

Topic

    Scott Heidenreich
    Find out if a signature control has been signedAnswered
    Topic posted April 11, 2019 by Scott HeidenreichBronze Trophy: 5,000+ Points 
    105 Views, 5 Comments
    Title:
    Find out if a signature control has been signed
    Summary:
    How do I determine if a signature control has been signed in OPA?
    Content:

    Hello,

    As a condition for being eligible to apply for a grant, I want to ensure the applicant has signed the signature control. The control is set to mandatory, however, that just throws and error message on the screen if they try to navigate away from the page. I do not want them to even be able to see the screen with the submit button on it until the signature is completed.  So I would like to be able to have a boolean attribute that can be set based on the status of the signature control.  Since OPA knows whether or not the signature control has been marked, how do I capture that information as a condition for the conlusion?

    Thank you,

    Scott

     

    Version:
    18D

    Best Comment

    Fiona Guy

    Ah... you're absolutely right. We've bumped up the priority on the issue (our ref: OZ-13352). 

    As a workaround, you could collect the signature on the Submit screen(s) itself - as hitting the Next/Submit button on the screen with the signature triggers the validation (which is why it's only an issue for "allow navigation in any order" interviews). You can have the same signature on multiple screens - you can keep the signature on your original screen and also have it on the submit screen. In addition - if you hide it from the submit screen using interview extensions your interview would look the same but the user would see the signature validation message (which is configurable) when the user attempts to submit without signing. I'll forward you an example. 

    Fiona

    Comment

     

    • Jasmine Lee

      Hi Scott,

      I just tried an example with a mandatory signature panel, and the interview wouldn't let me proceed to the next screen until I'd entered something in the signature panel.

      So if the Submit button were on the screen after the signature, I wouldn't see the Submit button until I'd filled in the signature.

      Does this suffice? Or is there other logic you need to use the signature panel for?

      Cheers,
      Jasmine

    • Fiona Guy

      Agree with Jasmine's comment. 

      If it's an "Allow navigation in any order" interview then you would have to make the signature box mandatory and have an attribute on screen (a boolean checkbox that acknowledges what they are signing, for example) which is then used to show/hide the submit screen. The boolean attribute could be hidden/set via interview extensions so not necessarily displayed to the user.

      We are considering whether controls like signature, and just visiting a screen generally, should trigger logic that can be used in rules, so it is on our longer term roadmap. 

    • Scott Heidenreich

      Ok. Thank you.  I've already been using the boolean approach you mentioned, however, the user can check the boolean without actually signing the control.

    • Fiona Guy

      Ah... you're absolutely right. We've bumped up the priority on the issue (our ref: OZ-13352). 

      As a workaround, you could collect the signature on the Submit screen(s) itself - as hitting the Next/Submit button on the screen with the signature triggers the validation (which is why it's only an issue for "allow navigation in any order" interviews). You can have the same signature on multiple screens - you can keep the signature on your original screen and also have it on the submit screen. In addition - if you hide it from the submit screen using interview extensions your interview would look the same but the user would see the signature validation message (which is configurable) when the user attempts to submit without signing. I'll forward you an example. 

      Fiona

    • Scott Heidenreich

      Thanks, Fiona.

      We actually have three different screens involved with signing and submitting an application.  Combining all three screens would make for a very long and busy screen.

      One screen is the signature itself with two boolean statements that have to be checked "Yes" along with the title and printed name of the person signing and the date and the signature control.  These elements are necessary, in part to comply with federal e-sign requirements.

      A second screen provides the warning that once the user submits the application it is no longer editable and has a boolean asking if they are ready to submit.

      The third screen is the screen with the actual submit button on it -

      This approach allows the user to focus on a single message per screen.

      It also allows me to know they clicked the next button so I can reload data from OSvC based on the state of the "do you want to submit?" boolean.  Reloading is necessary to verify that the application period is still open prior to offering the submit screen because the checkpoint saves the original state of the data from OSvC and won't refresh it without some kind of trigger. 

      Our applicants are in and out of their applications numerous times because they are often from very large organizations which necessitates them printing drafts, getting approvals, etc., prior to being able to submit. 

      So, being able to use the state of the signature control in a rule would be quite beneficial to ensuring we are getting a valid application.

      Thank you!