-
Posts
4,014 -
Joined
-
Last visited
-
Days Won
86
Content Type
Profiles
Forums
Enhancement Requests
Posts posted by Martyn Houghton
-
-
-
3 minutes ago, Victor said:
I have asked development to provide some or to add this back to the roadmap.
@Victor Thanks.
-
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
-
This seems to have got lost again, as not included in the latest Service Manager build.
Can we have a timescale for when this missing change will be released?
Cheers
Martyn
-
- 1
-
- 1
-
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
-
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.
Cheers
Martyn
-
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
-
At the moment you can Copy and Paste Nodes in the workflow editor between different workflows you have open on different tabs, but you cannot do this with the current copy-and-paste facilities on 'Custom Expressions'.
Can we request an enhancement to allow the copy and paste of expressions between different workflow editor sessions, the same way it works for nodes?
Cheers
Martyn
- 1
-
Any update on this, as supplier interactions are hardly ever (well for us) single binary event timelines in terms of response? There always will be a bit a back and forth when the supplier timer event timer will need to be paused but still active.
Cheers
Martyn
-
Is there any update on this?
Not being able to import on-premise customer assets and link them to the Organisations so we can see them when logging requests against contact at the said organisation is quite frustrating.
Cheers
Martyn
- 1
-
Looks like it did not make it into the latest Service Manager Build 2952, so would be good to have it documented in the roadmap.
Cheers
Martyn
-
- 1
-
Are the details now confirmed for the Hornbill User Group (HUG) session in November?
Did not want to start booking travel etc until they were.
Cheers
Martyn
-
Can this be put back into the Roadmap given it was incorrectly removed as being completed development?
Cheers
Martyn
-
-
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/resources/ideas_portal_users/create_a_portal_user
-
Thanks for the update. Whilst we await a new timescale, is there any information on the intended functionality change so we can prepare for this or even contribute to making the change more usable?
Cheers
Martyn
-
I now logged this as a Support Request - IN00179133
Cheers
Martyn
-
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
- 1
-
I trying to make the workflow easier to read/follow where you have crossing connections, especially so when to are looping back to earlier in the workflow.
Think of it like a multilayer PCB you have where you need to link back to somewhere else on the circuit board but not cross/short the connections.
Cheers
Martyn
-
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
- 1
-
Wait for Status Change - to trigger when SubStatus is changed
in Service Manager
Posted
@AlexTumber
Thanks for the detailed response. Fingers crossed for the 20th.
Cheers
Martyn