Ecrion Omni System is designed to provide you with a complete solution for managing your document production needs.  From giving access rights to members of your team to customizing your production workflow with custom code, Ecrion Omni System provides a platform for accomplishing any need from organizational to design.  This section is useful for giving you some good information on the best ways that our customers use Ecrion Omni System to meet the many demands of document production in an efficient and effective manner.

Start With The Setup

Before you start adding and editing the files in your projects, think about Ecrion Omni System as a management tool and how you will set up the Environments.  You may want to create an Environment for each of your customers, or perhaps you need to make an Environment for development, testing, and production.

 

Think about where your document design will begin and what type of path any edit must travel before it reaches production run and this will help you. We encourage you actually write down your Environments and list what types of actions will take place in each.  This process will begin to give structure to the organization of your document's production cycle, and then you can proceed with creating Environments for your users to work in.

Group Your Users

Make a list of your users ad categorize them by responsibility.  By grouping your users, you can manage the rights that each group of users possesses in one location and can eliminate the headaches associated with the administration of many users.  Once you've decided what users will be using Ecrion Omni System, proceed to the Users and User Group Management Modules section of the documentation to learn about setting up these accounts and configuring.  Log in to each account to test and check your specified settings.

Learn About Review and Approval Workflows

The Review and Approval Workflow feature in Ecrion Omni System allows you to structure the steps any project package must follow and which users need to review in order for that package to be approved and published to be used in production.  This features setup is also a part of your project planning and should follow after your user configuration.  Think about a simple modification like changing a template font. Then think about the parties that will need to be involved to review, test, and approve on all levels.  From there, you can learn about structuring your workflow in the Configuring Review and Approval Workflows section of the documentation.

Use Packages

Packages are a driving force behind much of Ecrion Omni System's capabilities.  We highly encourage the frequent use of Packages to preserve your projects at any time.  This ensures that you can always fallback to your project and all of its files in exactly the same state as when it was working the way you wanted.  You should encourage your users to use packages before making modifications and also after to initiate Review and Approval Workflows that you design.  This way, no edit will take place without being backed up or passed along for further review.  You can learn much more in the Working With Packages section of the documentation.

Use the Jobs View

Ecrion Omni System comes equipped with extensive logging directly available to you.  In the Working With Jobs section of the documentation, you can learn more about what information is available to you in the Jobs View of any project.  When you design your projects and test, it is important that you review your logs to ensure all tasks are performing as expected, and more importantly understand where to find the right information on where things may have gone wrong.