Jump to content

Ben Cook

Hornbill Users
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Ben Cook's Achievements

Rookie

Rookie (2/14)

  • Reacting Well
  • First Post
  • One Year In
  • Conversation Starter
  • Week One Done

Recent Badges

1

Reputation

  1. I'm seeing these "Possible Variable Reference Issues" warnings against many nodes when saving unrelated changes to workflows. The workflows still complete without errors. Have just raised a topic on this.
  2. Saving/publishing workflows is returning warnings against nodes which reference capture form fields, even where no related changes have been made: The capture form fields do exist (no changes have been made), and the workflows tested so far still complete with no errors. Using the variable picker to re-enter the same capture fields appends some new text which looks like a unique reference to the capture form, but saving/publishing still returns the same warnings: &[functions.pcf("customformdefaults","field_23_value")] &[functions.pcf("customformdefaults","field_23_value","pcf-270")] Is this a known issue?
  3. The latest update appears to have caused a few problems with our services: Requests cannot be raised from emails Our clinical single point of access team are missing some options under the service list, so are unable to raise requests (they've now moved to a non-Hornbill BCP) Some questions within progressive captures are asking for a value when one has been provided, so are unable to proceed
  4. We are using the external authorisation node (as most customers are "basic" rather than "user" accounts) within a business process for equipment requests. The "end user" and "approver" names are taken from user searches completed within the progressive capture, leading to some customers approving their own requests. Does anyone have a mechanism in place (other than a polite label, which we have) for preventing the same name being entered in both searches? We can obviously pick this up manually, however this creates more work. Thanks
  5. Is it possible to create a URL (in our case on a SharePoint page) to link directly to a progressive capture form? We can use a link to access the customer portal, but creating a link from within the specific PCF appears to require that same users credentials to access. Ideally we would have a URL to open the specific form after the single sign on page. Thanks in advance
×
×
  • Create New...