Jump to content

Search the Community

Showing results for tags 'fail'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Hornbill Platform and Applications
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Configuration Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Organisation


Location


Interests


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 4 results

  1. Thought the Request > Assignment >Assign to Owner (variable) node has a outcome indicator to pass whether it was sucessful or not, it doe not fail gracefully when it is not able to assign the requests based on the variable being passed. Instead it creates a BPM Error. Can the node be updated to continue the BPM but report the outcome as a failure. That way we can control how to handle it not being assigned in the BPM logic itself. Cheers Martyn
  2. Hello, Within one our our release tickets we have go an error stating "No matching gotoIf found" when looking it looked like the user may of pressed the wrong raise button and skipped the PC asking for the release type. The user re-did it and selected the release type but this still did not get pulled through. Nothing has changed within the BPM and other release tickets have been raised without any issues. I have added the release type from within the form in the ticket and re-tried last step but this will not work as it wont pull the info back through. Any help would be great thanks.
  3. We've recently had some network/infrastructure issues that have caused a massive amount of sent messages to fail - the latest one started this morning. Is there a way to attempt resending all failed messages, rather than going into each individual message? We've got thousands of these now.
  4. Is anyone else having issues with setting up the scheduling for reporting? Every time I do it, it comes up with this: I have created a Document by uploading a manually run report, with revision enabled, it is active, and published to the reporting library with document tags as suggested on wiki. Making sure that he document type is PDF and the report is publishing to PDF as well. And the report schedule is like this: But it just wont work, am I doing something stupid or is this a known problem? Hayley.
×
×
  • Create New...