Welcome to the Exact Product Blog

On this blog we will cover stories from all around the Exact ecosystem.

Posts Tagged ‘Exact Configurator’

Exact Configurator – Documents extension into SOI

Written by Michiel Dorjee on . Posted in Exact Synergy

Hi,

As I mentioned in my previous post I would get back to how we would handle documents extension in Synergy Office Integration (SOI).

Once you have created a documents extension and installed the SOI that belongs to release 252 your fields will be avaiable in the document type that you have made the field optional or mandatory in.
AddLinks

When you open for example your outlook and select an email to be uploaded of this document type, you will see that the field is also optional or mandatory from the SOI.
SOI Add Fields

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Within the SOI solution we encountered some limitations that we do support in the documents extension.
– Filtering in the browsers is not supported.
– Setting defaults is limited supported. You can not set a default with an expression or a reference. Of course this does work in the documents extension, but they will be ignored in the SOI solution.
– The fields in SOI have a specific display format, we can’t support all attributes that we do support in Synergy in SOI
– Four field types we were not able to support in this release in SOI: Image, Auto Increment, Sequence Number and Currency

We will work in the next release to getting this supported as well, but we didn’t want to postpone the release of documents extension for this.

Since Microsoft no longer supports Frontpage in versions later than 2007 we will also not support this in combination with configurations and SOI.

For our SDK developers that also would like to use the extension of documents and have it availabe in SOI you will need a Exact.PostInstaller.CSConfig.xml file. This file is already supplied by the configurator, but you can also create it yourself.
The contents of this xml file are quite simple and self explanatory for SDK developers.

Should you have any questions about this solution, do not hesitate to contact me at ruud.aalders@exact.com or add comments to this post.

Exact Configurator – Integration of workflow and business logic

Written by Michiel Dorjee on . Posted in Exact Synergy

Hi all,

Today I wanted to talk a bit about Exact Synergy Enterprise and workflow.
There are a lot of ways that workflow can be used in a company, but not with specific company logic.

In the next release of Exact Configurator we have enabled this, so that company logic can be incorporated into the workflow.
This can only be done by experts on the database, since you’ll need to have a knowledge of both SQL and the exact database.

What we have done is enable validation of the request at any step defined in the request, but also allocation of resources that can perform the next step in a request depending on business logic. I will explain with a small example.

Let’s take the vacation request, something which is done in every company. Standard we have a validation on fields in there, like start date can not be after the end date and things like that. But for a lot of companies there are rules out there that say, you can only take 3 weeks of vacation in a row, while in another company that is 2 weeks.

This kind of logic you can now incorporate into your configuration. We have created a tab called validation in the request definition. In there the consultant/expert can define business logic rules.
Note that eventhough our customers can see the rules once they have been deployed, they can’t create rules themselves. The reason for this is quite logical, if you define a query wrongly it can greatly affect the performance of your software, so let’s leave it to the experts!

Defining a rule is done through an intermediate screen and can be defined per step:

Once you have create the rule per step, it will appear in the overview screen.

This overview screen will also be seen by your end customer, except that the button new is not available for him. Your customer will be able to add rules (the rules that are inactive) and remove rules from a request type (this will make a rule inactive). Actual deletion of a rule can only be done by a consultant in his development environment.

The second option we have added is people allocation. Similar to the way validation rules are created also allocation rules are created.

Now, why would there be a need for people allocation combined with business logic, since you can already add a role to a request per step?

A good example for this would be the expense claim. Different rules apply in each company. Of course there is validation, which you can handle with the above mentioned explanation on validation rules, but there’s also an approval stage with rules applied to expense claims. For example an expense claim with an amount lower than 100 euros can be approved by the manager, but once the amount gets higher, usually specific finance people look at this. Or project specific declaration may need to be approved by a project manager.

These kinds of approvals you can arrange with our allocation rules. You can also have the request appear in multiple peoples workflow, simply by stating in your SQL statement that the resource is A OR B OR C.

With this software I think the expert has another strong tool to align the customers Exact Synergy Enteprise environment more and more with his business logic.

Happy configuring!

Should you have any questions about this solution, do not hesitate to contact me at ruud.aalders@exact.com or add comments to this post.

 

 

 

 

Exact configurator – Documents extension is coming!

Written by Michiel Dorjee on . Posted in Exact Synergy

As you may or may not know we have been working in release 252 for the extension of documents and I can happily announce that the feature will be available in release 252. This was quite a big project and I would like to congratulate our development team for delivering this software.

The documents extension will be working in the configurator engine in the same way as all the other extensions will work.

Select the extension for document.
DocumentExtend

There you can add your fields and buttons like any other extension.

The fields will be available in a new tab in the document types. For easy maintenance an new entry for document types has been created within the configurator, where you will only see the document types belonging to your configuration. Of course through the documents menu you can also modify existing document types.
LinkingDocType

 

 

 

At the document type level can be set whether a field is optional, mandatory  or not used. Linking a document type to your deployment set will deploy the document type to the end user environment and the fields used in your configuration.
AdditionalLinks

 

 

 

 

 

After setting the document type, the field will be available in the document. DocumentExtension

In the coming weeks I will inform you on how we will handle Synergy Office Integration.

Should you have any questions about this solution, do not hesitate to contact me at ruud.aalders@exact.com or add comments to this post.

PS: The extension will also be available for SDK developers!

Exact Configurator – Features for release 249

Written by Michiel Dorjee on . Posted in Exact Synergy

Hi All,

I briefly wanted to update you all on the main features we are releasing in the coming release (249) for the Exact Configurator. I will take you through the main changes for this release:

1. Added a button “Generate repository”
The reason we added this button is that when you want to update while you are configuring your solution, the repository wasn’t generated yet. As of now you have control to make sure your repository files are there and you can update your environment without losing your configuration.

2. Exposing web service
The web service for your entity can now be exposed. Please note that this doesn’t fully make your webservice work yet on a customer environment. You will need to do some configuration of your web service. More of this is explained in this document.

3. Implement Parent Child structure
Like the functionality that is currently offered on projects, this is now available in the configurator. You can link any entity to another entity and create a parent child sturcture.
For creating this in the configurator there are a number of steps to be taken:
– Create a parent entity (do NOT check the Use children option)
– Generate the entity
– Create a child entity
– Add a field of the type reference, referencing it to the parent entity.
–  Generate the entity
– Save a layout for the child entity (manage entity cards)
– Edit the ‘parent’ entity.
– Check the ‘Use children’ option
– Save the entity
– Add the child in the children section
– Re-generate the parent entity.
– Save the layout for the parent entity.
And as a result you have your parent child structure for your entities.

4. Message personalization
In the validation editor we have now created the possibility to enter your own error message.

5. Field type autonumber
With this field type you can autonumber your key field (which you can now change it’s type for as long as you haven’t saved your entity) and therefore hide it from your card and still have a unique record key.

These were 5 of our 18 product improvements for release 249.

Should you have any questions about this solution, do not hesitate to contact me at ruud.aalders@exact.com or add comments to this post.