Folder views and search results

Imagine that you want see attachments from many cases in one list. Now you can do it by creating "folder view". To achieve it you can create advanced search criteria, for example cases created in a given month. You can use form fields to group cases in folders. In example below you want to have first level of folders made it users who created cases and second level of folders made of month of modification.



In „Views and search result" you can see attachments added to cases, grouped by your criteria.



So it looks like disk folders but they are in fact virtually created from form fields or case properties. By hovering mouse pointed over a file (attachment) you can see preview of its content.



This makes it possible to create folder views or table views and access documents and cases very quickly.

Workflow conference in Warsaw

5th of July there will be a conference "DMS Systems and Workflows".
Entrance is free. Conference will take place in Radisson Blu Hotel in Warsaw.
Conference starts at 09:00 am. and finishes at 2:20 pm.

Multichoice in advanced search

There is one small but nice improvement in advanced search. It was easy to make a condition of type
a = 2 and b = 3
But if you made a condition like ...
a = 2 and a = 4 and b = 3
... you would get no results. But now if you put one field twice in conditions then AMODIT will know that they cannot be true at the same time and will change "and" to "or", so it will be in fact:
(a = 2 or a = 4) and b = 3

See example below:

Here there are two conditions put on "Case creator". They cannot be met at the same time and you would get no results but AMODIT automatically joins them with "or" and show both options in results.

2 ways to create dictionary from Excel file

It often happens that you have a dictionary (a list of items to choose) in an Excel file. One easy way to use it with AMODIT is to create normal dictionary in AMODIT and simply copy and paste values. If you select two columns in Excel and copy them to AMODIT then first one will be interpreted as "Name" and second as "Description". But this is static one-time copy, so further changes you will have to make in AMODIT.

But there is also other ways to get dictionary from Excel "live". So every time you change something in Excel file it will be synchronized by AMODIT. To achieve it you have to put your Excel file in a folder on server. Then you create "external dictionary" using Office driver. You just need to use proper connection string refering to Office driver and supplying Excel file's path (see picture below).
Then you need to place sheet name as table name with "[" at beginning and "$]" at end. You can refer to column names and their names have to be stored in first row of the sheet.

 

 

If you do it right AMODIT will read this file once a day and will synchronize dictionary. Quite easy and simple :)

D-Well (advertising media manufacturer) deployed AMODIT

D-Well is one of the major manufactures of advertising media for both Polish and international companies.

D-Well deployed AMODIT to support processes of producing tailor-made advertising products. It helps improve flow of information between employees and comply with deadlines.

Deployment took one month including integration of customer dictionaries with ERP system (Comarch Optima).

ShowSection() and HideSection()

Two new functions have been introduced to rules engine. They allow hiding and showing sections of a web form depending on certain conditions, f.e. value of other fields of a form and stage of a process.

So now there is a full set of such functions:
ShowSection(sectionName)
HideSection(sectionName)
ShowField(fieldName)
HideField(fieldName)

Extended "Get" function

Recently we have introduced new feature which is "Reference" field type. So now one case can reference another case. We think it can be useful to get some data from "referenced" case. Therefore "Get" function was extended to support it. Full desctiption of the function is shown below:

Get("table (>table>table...) | reference field","field title","(first|last|row number)")

Returns value of the given field from given row (by default first) of given table or from the case referenced in given field.

Function arguments:

• "table (>table>table...)" - names of table fields. You can specify nested tables by separating them by ">"
• "reference field" - name of the field with reference type
• "field title" - name of the field from table or from referenced case
• "(first|last|row number)" - (optional) from which row you want to get value. By default system return value from first row. For reference field this parameter is ignored.

---

Example 1:

Get("Positions","amount");
Positions is the name of table field.
Returns value of amount field from first row of positions table

Example 2:

Get("People","Name",3);
People is the name of table field.
Returns value of Name field from third row of People table. If there are less than 3 rows in this table, system will return value from last row.
You can use CountRows() function to determine how many rows are in this table.

Example 3:

Get("Invoices>Positions","ammount","last");
Invoices and Positions are table fields. Positions table is definied inside Invoices table.
Returns value of ammount field from last row of positions table definied inside invoices table (if there are many invoice rows, system will returns value from last invoice row). 

Example 4:

Get("Customer","Address");
Customer is the name of reference field.
Returns value of Address field from case selected in Customer field.