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

latest posts

In reply to: Maksymilian Stachowiak

Is that attribute by any chance in a group?
If so, have you set the permission restriction on group level too?

Yeha i mark every groups etc

But had information from support:

PL: Dzien dobry,
W przypadku widoczność kolumn na raportach dla kolumn listy pozycji, komunikat "Kolumna może być niewidoczna dla niektórych użytkowników" (ikona ostrzezenia w konfiguracji raportu) będzie wyświetlony zawsze, kiedy na atrybucie ustawiona jest jakakolwiek reguła ograniczająca widoczność, a obecność dowolnej reguły uniemożliwi wyświetlanie tej kolumny na raporcie (nawet jeśli w regule ograniczającej widoczność jest po prostu "TRUE", to i tak nie będzie widoczna na raporcie - jest to zamierzone działanie).
Checkbox o ktorym pan wspomina dziala tylko na pola naglowkowe jak mozna zauwazyc nie znajduje sie on na danych kolumnach listy pozycji.
Do naszej wewnetrznej aplikacji zostala juz zgloszona idea rozwoju w tym kierunku aby checkbox rowniez mogl byc wykorzystany dla kolumn listy pozycji.
Na ten moment dane z kolumn listy pozycji mozna wyswietlac wlasnie za pomoca kolumn wyliczanych tak jak pan to rozwiązał
ENG:
"Good morning,
Regarding column visibility on reports for item-list columns: the message "This column may be invisible for some users" (the warning icon in the report configuration) will always appear whenever the attribute has any rule restricting visibility set on it, and the presence of any such rule prevents the column from being shown on the report — even if the visibility-restricting rule is simply "TRUE", the column still won't be visible on the report. This is intended behavior.
The checkbox you mentioned only works for header fields — as you noticed, it's not available for item-list columns.
An idea to extend this functionality — so that the checkbox could also be used for item-list columns — has already been submitted to our internal application for development consideration.
At the moment, data from item-list columns can only be displayed using calculated columns, as you've already done."

Hello,

When I delegate an instance to another user, either via Delegate button or Substitutions, the user appears correctly in the CC section in the interface.

However, in Designer, under Values → System fields → Assigned people → CC, when I enter the instance number, the result is NULL. For Directly it works, it returns something..but for CC..nothing..

Is this expected behavior, or is there another way to retrieve the CC user for an instance?

Version: 2023.1.2.68

Thanks

In reply to: Maksymilian Stachowiak

Hi Marcin,
As far as I'm aware, Webcon allows only almost flat (an array item may have an object, which is flat, not nested) structure in this case (same as working with Invoke REST API Action).

You could try to use business rule to map some more nested structures using JSON features of SQL Server, but i'm not sure how it will impact generated OpenAPI/Swagger documentation generated by Webcon.

So based on your example this won't work by default mapping (would check if business rules help, but might have a negative impact on Swagger):
{
"suppliers": [
{
"hqAddress": {
"street": "Domaniewska 1",
"city": "Warszawa",
"postCode": "02-672"
},
"postAddress": {
"street": "Prosta 10",
"city": "Warszawa",
"postCode": "00-001"
}
}
]
}

But having something like this should work fine:
{
"suppliers": [
{
"hqAddressStreet": "Domaniewska 1",
"hqAddressCity": "Warszawa",
"hqAddressPostCode": "02-672",
"postAddressStreet": "Prosta 10",
"postAddressCity": "Warszawa",
"postAddressPostCode": "00-001"
}
]
}

We work on extensive processes, where the form scope is also a limitation for us. As a result, we often have to split a single process across several forms. We also do a lot of integrations, and the User-defined API has already been a lifesaver for us. It would be great to see support for domain entities, meaning the ability to receive and map more complex, structured objects (with nested objects and lists) directly onto the process data model, without having to flatten the contract or add intermediate parsing logic.

Are there any plans to extend the User-defined API or the data model in this direction? If this is on the roadmap, we would be grateful for any information on the expected timeline.

MVP

Hi Marcin,
As far as I'm aware, Webcon allows only almost flat (an array item may have an object, which is flat, not nested) structure in this case (same as working with Invoke REST API Action).

You could try to use business rule to map some more nested structures using JSON features of SQL Server, but i'm not sure how it will impact generated OpenAPI/Swagger documentation generated by Webcon.

So based on your example this won't work by default mapping (would check if business rules help, but might have a negative impact on Swagger):
{
"suppliers": [
{
"hqAddress": {
"street": "Domaniewska 1",
"city": "Warszawa",
"postCode": "02-672"
},
"postAddress": {
"street": "Prosta 10",
"city": "Warszawa",
"postCode": "00-001"
}
}
]
}

But having something like this should work fine:
{
"suppliers": [
{
"hqAddressStreet": "Domaniewska 1",
"hqAddressCity": "Warszawa",
"hqAddressPostCode": "02-672",
"postAddressStreet": "Prosta 10",
"postAddressCity": "Warszawa",
"postAddressPostCode": "00-001"
}
]
}

Hello,

We are using WEBCON BPS version [version, e.g. 2026]. We are building an endpoint with the User-defined API that receives a list of suppliers. Each supplier should be saved as a row in an item list on the form.
We would like to know whether the User-defined API can handle a structure where each list element contains nested objects, or whether we need to flatten it. I searched the forum for an answer but couldn't find a thread covering this case.

Structure 1 (nested, preferred):

{
"suppliers": [
{
"hqAddress": {
"street": "Domaniewska 1",
"city": "Warszawa",
"postCode": "02-672"
},
"postAddress": {
"street": "Prosta 10",
"city": "Warszawa",
"postCode": "00-001"
}
}
]
}

Structure 2 (flat):

{
"suppliers": [
{
"hqStreet": "Domaniewska 1",
"hqCity": "Warszawa",
"hqPostCode": "02-672",
"postStreet": "Prosta 10",
"postCity": "Warszawa",
"postPostCode": "00-001"
}
]
}

Questions:

1. Can the User-defined API definition map fields of nested objects (e.g. hqAddress.street, postAddress.city) to item list columns? If so, how should the input parameters be configured?
2. If not, is the flat Structure 2 the only option? Or is there another recommended approach, such as accepting the raw JSON and parsing it in an action or business rule?
3. Is support for nested objects inside list elements planned for a future version?

We would prefer Structure 1, because that contract is dictated by the external systems that will call our API.

Thank you in advance for your help.