Jump to content

Steve Giller

Hornbill Staff
  • Posts

    6,498
  • Joined

  • Last visited

  • Days Won

    268

Posts posted by Steve Giller

  1. As far as I'm aware "Security Error: 1" indicates that the system is unable to verify the session. Unfortunately this is always a generic message to avoid exposing security information.

    This could be as simple as a very brief connection drop preventing your session being authenticated for that transaction, so I think the best course of action would be to trap that error and re-present the data when the call returns a failure with this error (ensuring that this does not create a loop, of course.)

  2. 13 hours ago, Andrew Parsons said:

    i'm talking about using it to check an incoming email

    This would be done by the Auto Responder, and applied to the Request as an update. The Workflow would then come off hold and you could react to the content of the update.

     

  3. If you're using the Auto Responder to update Requests from email, you can put the Request on hold, configure the Service to select an "Open" substatus on update, and use a Suspend -> Wait for Off Hold node to respond to the incoming email. This does not prevent another action taking the Request off hold and triggering the Workflow to move on, however. 

  4. The "customer" account is a System account that manages the Customer Portal - this is not an account that can be directly interacted with and will always have an open session while there is any activity on the Customer Portal - even if this is just that someone has accessed the login screen, for example.

  5. I'd suggest:

    • Get the data for "customerGet"
    • Post that to the Timeline
    • Get the date for "analystGet"
    • Post both results to the Timeline

    That will at least confirm what you're getting from the "customerGet" and whether it's overwritten by the "analystGet"

  6. The variable displayed in your screenshot is from a node with e Result Reference of getRequestInformation, which is the default value for a Get Request Information -> Request Details node.

    I don't know where it's getting the data from, but it's not coming from either of your Get User Details nodes.

×
×
  • Create New...