Martyn Houghton Posted August 7 Share Posted August 7 Can I request an enhancement to add a 'Via' node to the Intelligent Capture flows. We make use of 'Via' nodes in the BPM to route connections between nodes is a clearer way, so the it is visually easier to follow and debug complex workflows. As we have also very complex shared IC's having the option would help in the same way here. Cheers Martyn 1 Link to comment Share on other sites More sharing options...
Berto2002 Posted August 7 Share Posted August 7 +1 but more generally for the UI and capabilities of Workflow and ICF designers to be gradually brought in line. Another example is the ability to right click on a line and insert node; and for them both to be called "Decision" not, as is the case, "Branch" in ICFs. 2 1 Link to comment Share on other sites More sharing options...
samwoo Posted August 7 Share Posted August 7 +1 to all the above. 1 Link to comment Share on other sites More sharing options...
David Paler Posted August 7 Share Posted August 7 +1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted August 7 Author Share Posted August 7 1 hour ago, Berto2002 said: +1 but more generally for the UI and capabilities of Workflow and ICF designers to be gradually brought in line. Another example is the ability to right click on a line and insert node; and for them both to be called "Decision" not, as is the case, "Branch" in ICFs. +1 to @Berto2002 comments on consistency. Link to comment Share on other sites More sharing options...
Gareth Cantrell Posted August 7 Share Posted August 7 +1 Link to comment Share on other sites More sharing options...
Steve Giller Posted August 7 Share Posted August 7 This is "on the list" internally - no timescales or confirmation of which elements are included as yet. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted August 7 Author Share Posted August 7 1 hour ago, Steve Giller said: This is "on the list" internally - no timescales or confirmation of which elements are included as yet. @Steve Giller Thanks for confirming. Link to comment Share on other sites More sharing options...
Peter Clough Posted August 8 Share Posted August 8 Will add my +1 to this. Good to hear it's already on the list though. 1 Link to comment Share on other sites More sharing options...
Gerry Posted August 8 Share Posted August 8 All, Thanks for the feedback and suggestions... We have added the "via" node into to Intelligent Capture We have added the feature that allows you to right-click a line and insert a node into that line/flow We have renamed the Branch node to be called Decision (not shown in video) We will also tidy up the context menu's they are a bit messy. These will appear in a release coming soon. https://www.loom.com/share/e4bd56ab2aeb4ba081fedfce2a38cbc2 Gerry 5 2 Link to comment Share on other sites More sharing options...
samwoo Posted August 8 Share Posted August 8 Brilliant @Gerry! Also Loom seems useful, is this something Hornbill will use going forward? Link to comment Share on other sites More sharing options...
Gerry Posted August 8 Share Posted August 8 @samwoo Quote Also Loom seems useful, is this something Hornbill will use going forward? Loom is something I have taken to using internally mostly, its far quicker to communicate product changes visually and Loom make it pretty easy to create a one-take screen recording. As for more general use at Hornbill, probably not so much in the short term, we are not awash with people who are comfortable or eager to make these types of videos, I would love to see is using tools like Loom more. We have integrated Loom into Hornbill for embedded content, so in timelines you can share loom videos as embedded content, so its something we can use more of. As you probably know, our Academy e-learning initiative is gaining momentum, as is our Documentation (docs.hornbill.com) initiative, my primary strategic driver is centred around "enabling others", so documentation, academy (e-learning), product streamlining and simplification for use, administration, customisation are all underway, and the enabling of Citizen developers around Platform ESM type functionality all fall under this initiative. Forward hiring strategy is focused in on these areas. My goal is to enable as many people as possible (customers, partners, consultants, our own people and new hires) to be Hornbill experts in their own right. Gerry 2 Link to comment Share on other sites More sharing options...
Estie Posted August 16 Share Posted August 16 @Gerry - The changes above are great additions. However I do not seem to be able to find the option to insert a node between the current nodes in an IC, no matter how carefully I right click over the line. Also not sure if some of the above changes recently made are affecting workflows. Yesterday I noticed some decision nodes in a workflow where the description of the node showed them to be named as 'Branch', while others were showing as 'Decision' I also moved some decision nodes around in a workflow using copy and paste and today I have gone back to the workflow and they are now showing as 'Object Object'. Should this be the case? 1 Link to comment Share on other sites More sharing options...
Gerry Posted August 22 Share Posted August 22 @Estie I expect that was just a timing issue - I trust you can see the option now? Gerry Link to comment Share on other sites More sharing options...
Estie Posted August 22 Share Posted August 22 @Gerry - No unfortunately not. The via node option is also not appearing for me. I will raise a support ticket. Link to comment Share on other sites More sharing options...
Steve Giller Posted August 22 Share Posted August 22 12 minutes ago, Estie said: The via node option is also not appearing for me. I'm pretty sure the release that includes these options has not yet been released to Live. Link to comment Share on other sites More sharing options...
Estie Posted August 22 Share Posted August 22 @Steve Giller I got the impression from the above that it had been released already. Any idea when this might be? Is this related? Link to comment Share on other sites More sharing options...
Martyn Houghton Posted August 22 Author Share Posted August 22 Also shows as completed in the Platform Roadmap. Link to comment Share on other sites More sharing options...
Steve Giller Posted August 22 Share Posted August 22 I'm sure the Platform code is complete if that's the case - however, I believe it's Core UI (or possibly SM, or both) that presents it to the end user and that release is not yet live. Link to comment Share on other sites More sharing options...
Steve Giller Posted August 22 Share Posted August 22 46 minutes ago, Estie said: Is this related? Yes, however this is the underlying validation to prevent there being issues when it is released - a bit like laying the foundations of a house before building the walls. Apologies for any confusion. 1 Link to comment Share on other sites More sharing options...
Gerry Posted August 22 Share Posted August 22 Sorry for any confusion here, as @Steve Giller mentioned above, in order to release some features (like this one) there are two main projects that have to be released, the first is the Hornbill Platform, this is what the above roadmap relates to. Secons is what we call Core UI, these are the pages/screens you see in your browser, this is the project that has the Admin pages, which includes the workflow designer. Not relevant to this particular conversation, but in addition, sometimes we add features to Service Manager application, which is also its own project, that may have dependancies on Core UI and/or the Hornbill platform, so features that depend on other layers are generally programmed to active once the right build numbers of dependant layers have been reached. In this case, the Hornbill Platform changes (basically changes to the workflow processing engine for this change) have been made, and have worked through to live (what customers get) already The changes in Core UI (which is the BPM designer) has been modified and is currently sitting on Beta, that means we have it internally, our partners have it, but its not in general production as of yet. Each project has its own release schedule, generally speaking we have a timeframe of Build-to-Test=immediate, Test-to-Dev=once automation tests complete(hours normally, or tests fail), Dev-To-Beta=after 24 hours of being in Dev and not being blocked, Beta-to-Live=after 48 hours of being in Beta and not being blocked). We block releases in the pipeline if any test fails or any defects are found. At the moment, we are still awaiting a Core UI release, which is currently in beta but has been rejected, presumably because we have found something else that is not ready for live. So there is a bit of a delay, but it IS in the pipeline so will appear very soon. Specifically, when the UI build is greater or equal to 2219 Gerry 1 Link to comment Share on other sites More sharing options...
Estie Posted August 23 Share Posted August 23 @Gerry @Steve Giller Thank you. Might seem a silly question but whilst we are on the subject, what does ESP mean? Link to comment Share on other sites More sharing options...
Will Darley Posted August 23 Share Posted August 23 +1 Link to comment Share on other sites More sharing options...
Gerry Posted August 23 Share Posted August 23 @Estie It means "Enterprise Services Platform", its basically the nickname we use to identify the "Hornbill Platform", previously used as an internal dev codename. Hornbill is a layered application which basically looks like this Cloud -> Hornbill (ESP) Platform -> Application(s) So our Cloud environment is akin to our own version of Amazon Cloud Services (database, storage, compute, front end servers, other infrastructure and all that cloudy sort of stuff), unlike most vendors we run our own cloud environment on bare metal, this gives us certain economics and full control over our security posture and scalability without crippling ourselves with costs for "the Cloud tax" that a lot of SaaS companies can suffer as they scale. We also do use traditional cloud services for some things, primarily backups and resilience type requirements. The technical people at Hornbill that build, maintain and support our cloud environment are DevOps engineers with expertise in networking, internet technologies, all things Windows and Linux, enterprise storage as well as cloud and enterprise security systems and practices. The Hornbill (ESP) Platform is the base of our application layer, its where all the Hornbill core capabilities live, like email, workflow, integrations, automations, administration, and low-level technical stuff like authentication (SAML, OAuth etc), the app store for deploying applications onto the Hornbill Platform, and a myriad of modules and functional capabilities that make it possible to build applications without application developers having to create all this reusable functionality. The platform without an application does not do very much thats useful, until you install one or more applications onto it. Think about your mobile phone out of the box, it can make and receive calls, it deals with all the technical issues like radio comms, encryption, storage, basic functions and so on, and an app store, then you install the apps that you want on your phone and it becomes a personal hand-held computer thats meets your specific needs. You can think of the Hornbill Platform like the Phone ready for you to install the business apps that will make Hornbill useful for your requirements. The technical people at Hornbill that build, evolve and support our platform are focused on things like platform capabilities, performance, scalability, enabling application developers with tools, systems, processes, build, test, deployment systems, testing tools and systems, test automations, common functions, modules, services, API's, integrations, security and cloud enablement technologies, as well as our CoreUI (the screens you see when you log into Hornbill), there is also some technical overlap between the Hornbill Platform and Cloud teams, often working key services, protocols and other deeply technical issues/implementations. Hornbill applications, like Service Manager, Customer Manager, Project Manager, Boards Manager and so on, are business applications, focused on a specific set of capabilities. The basic idea is, the Hornbill Platform aims to abstract away all of the technical complexities of building a scalable SaaS application, allowing our application development teams to focus on the application domain instead of the low-level complex technical details they would otherwise have to implement, or use others tools/systems for. So for example, for Service Manager, the developers do not need to worry about the intricacies of how SSO or Email protocols or the deployment and test automation, distributed front ends, infrastructure, databases, storage and so on, thats all taken care of in the lower layers of our stack. Instead the Application Developers can focus more on the application domain, customer needs and business value delivered. This is why Hornbill has multiple roadmaps, because each layer and each application, generally speaking has a different team behind it, each layer is basically developed independently of any other layer, so things get developed and released at different rates which is why its very easy to lose track of where everything with every dependancy in every release pipeline is at any given point in time. Probably more than you wanted to know, but now you know I should probably turn this into a LinkedIn Post! Gerry 1 Link to comment Share on other sites More sharing options...
Gerry Posted August 23 Share Posted August 23 In fact, I put into a blog post, for others that might also be curious about the ESP name or our high level tech stack, and why we have such a stack. https://www.hornbill.com/blog/what-does-hornbill-esp-stand-for Gerry 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now