WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question
Home > Forum > Latest posts

latest posts

MVP

Hi,
That sounds strange. In my opinion, you're doing it right.
The method you described should work – adding domain groups to dictionary items means users can see ONLY the items they have permissions for.

I tested it, and that's exactly how it works – I can only see the items I have permissions for (the "Access to data in the context of the system account" option should be disabled, of course).

When you access a dictionary item in administrative mode, do you see the assigned AD group in the permissions section?

Hi everyone,

I have a dictionary process where I assign values to specific attributes. Then I use the source containing all dictionary elements as the data source for an attribute, filtering the values based on another attribute specified on the dictionary item. These values are then available to users as a dropdown list.
However, I would like to make some of these values unavailable for certain users — in other words, specific users should not see or be able to select certain values from the dropdown.

I tried the following approach:
I created an action that grants read permissions on each dictionary item to domain users.
On the data source, I disabled the "Access to data in the context of the system account" option.

However, after doing this, users see "No matches found" instead of the available values.
Is there a recommended way to configure this so that the dropdown only displays the dictionary values that the current user is authorized to see?

Thanks in advance for any advice.

In reply to: Sébastien Anselment

Hi Matthias,

sounds good. Glad I could inspire you a bit. Thanks for sharing.
I‘ve one question:
Why isn‘t the status coming or derived from ERP and needs to be set by a WEBCON user (probably without writeback to ERP)?

Kind regards,
Sébastien

The sales representatives do not have acces to the ERP System. By using WEBCON I don't have to worry about VPN access to restricted Systems, beacuse they simply use a browser or the app while beeing on customer visits. Furthermore there is no status field in the ERP.
So that's why I solved this in WEBCON. We simply create the offers in the ERP and in case of an order we also create that in the ERP. The ERP itself doesn't care weather an offer has been won or not. :)

Best regards,
Matthias

MVP
In reply to: Matthias

Hello there,

I would like to share how I implemented an offer tracking solution in WEBCON using a Dictionary workflow and data imported from our ERP system.

Background:
The goal was to provide our sales representatives with a simple overview of all open offers while ensuring that each offer is imported only once and can be managed directly within WEBCON.

Solution Architecture:
The implementation is based on a Dictionary workflow that acts as a central repository for all imported offers.

A global action runs automatically during a nightly job and starts a SQL stored procedure. This procedure retrieves all relevant offers from the ERP system and imports them into WEBCON.
To prevent duplicate entries, the stored procedure checks whether an offer already exists before creating a new record. As a result, each offer is imported only once and remains available for further processing.

User Access and Filtering
Each offer contains information about the responsible sales representative.
Using predefined report filters, every salesperson can access only the offers assigned to them, while all offers are stored in the same Dictionary workflow. This eliminates the need for separate workflows or data structures.

Status Management
Since every offer exists as a single record and remains in one workflow step, I do not require a complex workflow process.
The sales representative can simply update a status field, for example:
-Open
-Won
-Lost
The main report is configured to display only offers with the status Open. Once an offer is marked as Won or Lost, it automatically disappears from the working list but remains available for historical reporting and analysis.

Benefits
-Automatic nightly synchronization from the ERP system
-Each offer is imported only once
-No duplicate records
-Simple status management
-User-specific visibility through report filters
-Clear separation between open and completed offers
-Full historical traceability

I would be interested to hear how others have implemented similar ERP offer tracking scenarios in WEBCON and whether there are alternative approaches that provide additional advantages.

@Sébastien: Thank you very much for your help and inspiration!

Best regards,
Matthias

Hi Matthias,

sounds good. Glad I could inspire you a bit. Thanks for sharing.
I‘ve one question:
Why isn‘t the status coming or derived from ERP and needs to be set by a WEBCON user (probably without writeback to ERP)?

Kind regards,
Sébastien

In reply to: Sébastien Anselment

Hi Matthias,

it's not that simple to understand your requirement.

I understand that you have a MSSQL Data Source in WEBCON that already gets the offers from your ERP and you wish a view in the portal to display/analyze this data.

Unfortunately data sources can't be used as sources in reports yet as you've mentioned already.

The workaround I use to just display data from data sources is as described.

Create a process "Offer Tracking"
Add a form field of type "data table" and select the MSSQL ERP data source.
Configure the advanced configuration to select the columns to be displayed and other options.

Unfortunately data table form fields have no filter or search options in the portal like they exist for reports.

If you need filtering you need to add further form fields.
E.g. a form field of type choice picker as dropdown.
As its data source you choose the Current MSSQL Connection and insert e.g. this query

SELECT *
FROM (
VALUES
(10, 'won'),
(20, 'lost'),
(30, 'in progress')
) AS t (stateId, State);

If you want the states to be read directly from the data source you need a business rule "BR-ERP-states" with data source value to get the state values as returned column and place the data source value in a DISTINCT.
Then use this query to populate the state filter dropdown instead of the above query:

SELECT item
FROM dbo.splitToTable('##BR-ERP-states##',';')

Select the business rules through the functions tab to include it to the query.

If you want to use the business rule value in a data source filter you need to write this business rule to a multiline text form field set as technical field. This is needed because no business rules are supported in data source filters. You could now also put this technical field in the above query instead of the business rule.

Now you can use the state filter field in the data source filter of the data table field to match the data source column with the state to the state form field.

Use the similar procedure for other filtering needs.

To deactivate the unsaved data alert when leaving the form you can follow this blog post:
https://sebastien-anselment.github.io/blog/posts/2025/06/30/disable-unsaved-data-alert-when-leaving-a-form/

If you want the comfort of reports you can also create a dictionary process with a form field for each relevant column of the ERP data source and use a cyclical timer in global actions to import/update the ERP offer data to the dictionary. This way the data is replicated e.g. once per day. This reduces traffic with ERP but leads to a loss of realtime data.

I hope this helps you a bit.

Kind regards,
Sébastien

Hello there,

I would like to share how I implemented an offer tracking solution in WEBCON using a Dictionary workflow and data imported from our ERP system.

Background:
The goal was to provide our sales representatives with a simple overview of all open offers while ensuring that each offer is imported only once and can be managed directly within WEBCON.

Solution Architecture:
The implementation is based on a Dictionary workflow that acts as a central repository for all imported offers.

A global action runs automatically during a nightly job and starts a SQL stored procedure. This procedure retrieves all relevant offers from the ERP system and imports them into WEBCON.
To prevent duplicate entries, the stored procedure checks whether an offer already exists before creating a new record. As a result, each offer is imported only once and remains available for further processing.

User Access and Filtering
Each offer contains information about the responsible sales representative.
Using predefined report filters, every salesperson can access only the offers assigned to them, while all offers are stored in the same Dictionary workflow. This eliminates the need for separate workflows or data structures.

Status Management
Since every offer exists as a single record and remains in one workflow step, I do not require a complex workflow process.
The sales representative can simply update a status field, for example:
-Open
-Won
-Lost
The main report is configured to display only offers with the status Open. Once an offer is marked as Won or Lost, it automatically disappears from the working list but remains available for historical reporting and analysis.

Benefits
-Automatic nightly synchronization from the ERP system
-Each offer is imported only once
-No duplicate records
-Simple status management
-User-specific visibility through report filters
-Clear separation between open and completed offers
-Full historical traceability

I would be interested to hear how others have implemented similar ERP offer tracking scenarios in WEBCON and whether there are alternative approaches that provide additional advantages.

@Sébastien: Thank you very much for your help and inspiration!

Best regards,
Matthias

In reply to: Timer Clock

The screenshot shows the **Admin Trace Session** section, so it is normal for the list to be empty if no diagnostic session was started beforehand.

Could you please share a screenshot of the **Generate/Update Word file** action configuration? Please check the selected template and all dynamic values, as one of them may be referencing a field, template, attachment category, or another element that no longer exists.

Please also let us know exactly when the error occurs and whether the same template works correctly in another process. Make sure to hide any sensitive information in the screenshot.

If the error occurs while using **Generate Documentation** in Designer Studio, rather than when the action is actually executed, please mention this as well, since these are two separate functions.

Thanks for the update. Since the **Admin Trace Session** list is empty, it likely means no diagnostic session was running at the time, which is expected.

To help troubleshoot the issue, could you please share a screenshot of your **Generate/Update Word File** action configuration? Please include the selected template and all mapped dynamic values, as one of them may be referencing a field, template, attachment category, or another element that no longer exists.

Also, please let us know:

* At what exact step does the error occur?
* Does the same **Generate/Update Word File** template work correctly in another process?
* Does the error happen while using **Generate Documentation** in Designer Studio, or only when the **Generate/Update Word File** action is executed?

Kindly blur or hide any sensitive information before sharing the screenshots.
https://timerclock.io/

In reply to: Franek

Unfortunately, I have old documents that use standard comments. I do not want to manually delete all comments in the old elements and move them to the new attribute.

Hello Franek,

As Jacek mentioned, you can use a "Multiple line of text" field, then create a cycle with the "Change value of single field" to copy all comments, and finally hide the standard comments field.

In reply to: Łukasz

The screenshot shows the Admin trace session section, so it is normal that the list is empty if no diagnostic session was started earlier. Search logs by GUID will only be useful if you have the error GUID.

Could you share a screenshot of the Generate/Update Word file action configuration? Please check the selected template and all dynamic values, as one of them may refer to a field, template, attachment category, or another element that no longer exists.

Please also let us know when exactly the error occurs and whether the same template works in another process. Remember to hide any sensitive information in the screenshot.

If the error appears when using Generate documentation in Designer Studio, rather than when the action is executed, please mention this because these are separate functions.

The screenshot shows the **Admin Trace Session** section, so it is normal for the list to be empty if no diagnostic session was started beforehand.

Could you please share a screenshot of the **Generate/Update Word file** action configuration? Please check the selected template and all dynamic values, as one of them may be referencing a field, template, attachment category, or another element that no longer exists.

Please also let us know exactly when the error occurs and whether the same template works correctly in another process. Make sure to hide any sensitive information in the screenshot.

If the error occurs while using **Generate Documentation** in Designer Studio, rather than when the action is actually executed, please mention this as well, since these are two separate functions.

In reply to: Ruxandra Bacov

I checked Administration Tools, but I can't see any Event Log entries. Please see the attached screenshot. We have the Version 2023.1.2.68.

The screenshot shows the Admin trace session section, so it is normal that the list is empty if no diagnostic session was started earlier. Search logs by GUID will only be useful if you have the error GUID.

Could you share a screenshot of the Generate/Update Word file action configuration? Please check the selected template and all dynamic values, as one of them may refer to a field, template, attachment category, or another element that no longer exists.

Please also let us know when exactly the error occurs and whether the same template works in another process. Remember to hide any sensitive information in the screenshot.

If the error appears when using Generate documentation in Designer Studio, rather than when the action is executed, please mention this because these are separate functions.