Jump to content

Martyn Houghton

Hornbill Users
  • Posts

    4,014
  • Joined

  • Last visited

  • Days Won

    86

Posts posted by Martyn Houghton

  1. @HHH

    We publish quite a few documents via the Customer Portal at the Services level. 

    Just be aware there are a few limitations at the moment.

    • You cannot reorder them (without unlinking and then relinking them in the order you want).
    • You cannot group documents or have a hierarchy, it is just a single list in the order you link them. We end up uploading zip file of documents as groups, but then you cannot view them individually.
    • Unlike all the other options on the Service Portfolio form, only the 'Service Owner' can link/unlink documents so you have keep changing the Service Owner between the people whom administer the service.

    Cheers

    Martyn

    image.thumb.png.2876dd69bb06d96d5fb2251cb1de2b04.png

  2. When searching for a Service via the Employee Portal, it has the same issues as per the Customer Portal with the resulting matching services always displayed in serviceId ascending order rather than search results relevancy. Therefore your new services will always be at the bottom of the results list, no matter how precise you make your search criteria, making it hard for customers to use the search facility to locate the correct service to log requests under.

    Can the search results apply common practice and display the results in relevancy order.

    Cheers

    Martyn

    image.thumb.png.7ad97be0a47166950fdeb6e2452aa585.png

     

     

  3. Following on from my post a moment ago, can we also request an enhancement to add support for more complex logic, i.e. ability to use multiple hierarchical 'AND' and 'OR' logic with sub-criteria in brackets?

    At the moment in IC Branch conditions, you can only have a single level of conditions expressed sequentially, whereas in the Decision conditions in workflow, you can use brackets to have multiple levels of logic criteria.

    image.png.984d75a277a88699b381226dbf2f6e6f.png

    Cheers

    Martyn

     

  4. Along the same lines as my post below, can the Intelligent Capture Branch Conditions fields be extended to include CatalogID in addition to the current Catalog Name.

    We want to standardise on using Catalog ID rather than the Catalog Name, in the branches in our IC's so when the name is changed we do not need to update the branch conditions. Also having an ID value makes it use the 'is in' option. 

    Cheers

    Martyn

     

  5. Can we request an integration enhancement to add support for Aha! Roadmap Software, in particular, the following methods for the administration of 'Portal User'.

    We use Aha! for interaction with our large user base to publish product roadmaps and collaborate with customers on new functionality/RFC's.

    We want to automate the creation, updating and removal of Aha! Portal users from requests logged via Service Manager Portals.

    • Create a portal user
    • Create a portal user with 
    • Delete a portal user
    • Update a portal user

    Cheers

    Martyn

    References

    https://www.aha.io/api

    https://www.aha.io/api/resources/ideas_portal_users/create_a_portal_user

  6. On 9/22/2023 at 1:44 PM, Gerry said:

    ok so your saying, an actual node (like a label in a schematic tool) that simply points to a via node. So nia nodes would need to have unique identifiers so you could select the via to goto.  Is that what you are saying?

    @Gerry Yes thats the idea, 'Goto Via' rather than 'Goto Next Stage'. Having the ability easier read and follow the workflow without a spaghetti of crossing links make the workflow easier to maintain in my opinion.

    We are not going to get away from complex workflows hence the idea of making them easier to visualise.

    Cheers

    Martyn

    • Like 1
  7. With the ever-growing complexity of our BPMs we very often have a large number of crossing node connections, even using Via nodes to try to space these out, can make the workflow still very hard to follow.

    Can we raise an enhancement request to have a 'Goto Via' set of nodes similar to the 'Nest Stage' node, which essentially goes to a 'Via' node or similar within the same stage. Then there could be a setting in the editor to either display the links from the new node (perhaps as a dotted line) or hide them?

    Cheers

    Martyn

    image.thumb.png.2b2bfcffb37c389031ae7d5133b29512.png

    • Like 1
×
×
  • Create New...