AMODIT has two main types of users: internal and external. Internal users are usually employees and they have access to almost all features (except for administrative ones).
External users are usually people who interact with the system and play some roles in processes but they are not employees. For example they can be customers, potential customers, applicants etc. They have limited access to functionalities and only to selected procedures.
Important difference between these types of users is also that external users create accounts themselves and do NOT need to be acepted nor verified. During registration external users create external organizations and then manage them.
In new version of AMODIT there are some new options for customizing interface for external users. For example you can define which fields show up on registration form. And also you can decide which functionalities should be hidden.
Thursday, October 25, 2012
Wednesday, October 24, 2012
Programming trick
Here is some example how you can use sofisticated programming features of AMODIT.
Let's say you want users to choose option from dropdown list and then set some parameters value depending on that choise. Of course you can use bunch of "if-then" statements to achieve it. But it will make code of the rule quite long and not so easy to maintain and to make changes.
Smarter and more tricky way is to put different value of parameters in descriptions of dictionary items. Look at picture below. It is in Polish but focus on syntax of descriptions (column "Opis").
OK, but how to extract value of parameters from it. You can do it using proper Regular Expression:
desc=GetDictionaryDescription("DictionaryName");
parameter=RegExp(desc,"param1=(?<param1>[0-9,. ]*)","param1");
It looks pretty complex but saves a lot of code and makes changes easy...
Let's say you want users to choose option from dropdown list and then set some parameters value depending on that choise. Of course you can use bunch of "if-then" statements to achieve it. But it will make code of the rule quite long and not so easy to maintain and to make changes.
Smarter and more tricky way is to put different value of parameters in descriptions of dictionary items. Look at picture below. It is in Polish but focus on syntax of descriptions (column "Opis").
OK, but how to extract value of parameters from it. You can do it using proper Regular Expression:
desc=GetDictionaryDescription("DictionaryName");
parameter=RegExp(desc,"param1=(?<param1>[0-9,. ]*)","param1");
It looks pretty complex but saves a lot of code and makes changes easy...
Monday, October 15, 2012
New certified specialists
One of our customers decided to certify own employee to maintain AMODIT inside organisation. They have passed exams and became certified AMODIT specialists. Congratulations!
License price calculator
At www.amodit.com you can find license price calculator. It became necessary because now price depend not only on number of users, but also on number of processes. Feel free to use it!
Monday, October 8, 2012
New price list
Pricing for AMODIT has changed. It is now more flexible.
Please have a look at current price list: http://amodit.com/en/For-customers/Licences-and-hosting.aspx
Please have a look at current price list: http://amodit.com/en/For-customers/Licences-and-hosting.aspx
Tuesday, October 2, 2012
Hiding form fields "on the fly"
Sometimes it would be nice to show or hide a field depending on some conditions. For example depending on value of other field. Typical situation is when you have a drop down list with various choices but last one is "Other". When user chooses this option it is nice to show a field to let her/him type what "Other" really is.
And a good news is that from version 1.8.5 you will have such option. There two new functions:
HideField("fieldname")
and
ShowField("fieldname")
So you can use automatic rule to show or hide fields.
Note: To make it work well automatic rules are now also fired just before showing a form.
And a good news is that from version 1.8.5 you will have such option. There two new functions:
HideField("fieldname")
and
ShowField("fieldname")
So you can use automatic rule to show or hide fields.
Note: To make it work well automatic rules are now also fired just before showing a form.
Monday, October 1, 2012
Qualia Development deploys AMODIT in a cloud model
Qualia Development is a developer with twelve years of experience, the company belongs to a PKO BP bank group. Qualia is known for its high-quality projects in the housing market, it can also boast of the fact that is the first and only developer in Poland building a network condohotels managed under the Golden Tulip hotel brand.
Another assumption was to use the existing network scanners and minimal interference with users' workstations, thus the use of a Web application.
Powerful modeling methodology has allowed an efficient mechanism to implement the service in accordance with pre-established plan.
Key factors for the decision were:
Most of the work related to defining workflow processes have been carried out by the expert staff of Qualia, which allowed a short time to reflect business requirements.
Challenge
Qualia Development strives for continuous improvement and optimization of business processes. One of the challenges is a matter of efficient workflow and approval of cost documents. This is particularly important because of the geographic spread of the company. Invoices received in different locations are to be scanned, described, validated and transmitted to the headquarters to handle the payments and accounting.Another assumption was to use the existing network scanners and minimal interference with users' workstations, thus the use of a Web application.
Deployment
After reviewing the available solutions on the market Qualia decided to implement the AMODIT system (www.amodit.com). It is an innovative system that allows you to quickly search for information on the so-called metadata (the relevant parameters) and the contents of the documents, including the mechanisms of OCR (Optical Character Recognition). With the introduction of innovations in the field of document workflow, system logs all changes in documents’ content as well as monitoring their life cycle. In addition, significantly transferring documents between users have been facilitated.Powerful modeling methodology has allowed an efficient mechanism to implement the service in accordance with pre-established plan.
Key factors for the decision were:
- flexibility of the system allowing Qualia to independently model new workflows,
- ability to run solutions in the "cloud computing" on the basis of a monthly fee, while preserving the possibility of transferring all to own on-premise servers at any time.
Most of the work related to defining workflow processes have been carried out by the expert staff of Qualia, which allowed a short time to reflect business requirements.
Subscribe to:
Posts (Atom)