With our Luna Workflow Management System (WMS) release right around the corner and with so much to demonstrate; we decided to reveal a few items before the main release.
Luna WMS features a rich Rest API enabling integration in to all sorts of system; businesses that we have work with that have adopted Luna WMS have seen significant changes to their internal business operations enabling them to rapidly scale to meet market demands and reduce the technical hurdles behind iterative updates to workflow.
To aid in introducing Luna WMS we intend to publish several articles covering key areas within Luna and how they can be utilised to improve data capture and workflow. Topics we have planned include:
- Designing an enquiry (also known as case or matters) process:
- Per-case type designers; each separate case/enquiry type can provide their own questionnaires.
- What does the system agent see?
- Rest API functionality.
- The document templating system:
- Building document templates and the template tagging system.
- Demonstrate optional AI integration using Rhea Framework that can generate/improve upon document templates on behalf of user.
- Template approval system
- Electronic signature support and real-time notifications
- Document libraries
- Building document templates and the template tagging system.
- The Rest API in greater detail
- Demonstrate enquiry creation through the Rest API; and how to processes/progress a file through automations.
- Luna’s Rest API makes integrations in to third-party systems such as Proclaim trivial (obviously assuming you know how to consume Rest services, if not don’t worry we can help).
There’s so much more Luna can do but by focusing on these areas initially we hope to impress upon you the advantages to using Luna and demonstrate how efficiently you can prototype new workflows and seamlessly make them live.
Here is a collection of screenshots from Luna WMS
** Note to existing businesses using Luna WMS and/or derivatives (private forks, etc.) unless you are using the Luna WMS framework directly from ourselves (Oddineers Ltd.) the public API documentation shown here may/will differ significantly to your own private fork; especially true the greater the time that has passed since the fork.
Thanks for reading; if you have any questions please consider reaching out to us.
