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

latest posts

In reply to: Karol Częczek

Ok I see where you have a mistake, don't use the alias d. for a column in split to table because you get this result for the generated code
cast(d.dbo.ClearWFElemAdv(DET_

you can do it like this : dbo.SplitToTable(CAST(dbo.ClearWFElemAdv(d.{DCNCOL:1173}) AS NVARCHAR(MAX)), ';') AS ST

Hi,
thank you for help and direction.

I don't know why, but "STRING_SPLIT" is not working ...
(did not recognize function ect. .. with declare I have got the same problem ... - maybe not set proper rights in database .. I don't know)

but dbo.SplitToTable works :D

any way in my scenario the proper code is:

[code="SQL"]
SELECT
a.DET_WFDID AS 'ID elementu',
{DCNCOL_NAME:1174} AS 'Kategoria',
ST.Item AS 'Punkt pytania'
FROM
WFElementDetails a
CROSS APPLY
dbo.SplitToTable(CAST({DCNCOL:1173} AS NVARCHAR(MAX)), ';') AS ST
WHERE
a.DET_WFDID = {WFD_WFDID}
and a.DET_WFCONID={WFCON:3749}
AND a.DET_IsDeleted = 0 -- Opcjonalnie, aby pominąć usunięte wiersze

[/Code]

and for Attribute in form (not Item list):

[code="SQL"]
SELECT
a.WFD_ID AS 'ID elementu',
ST.Item AS 'Punkt normy'
FROM
WFElements a
CROSS APPLY
dbo.SplitToTable(CAST('{3654}' AS NVARCHAR(MAX)), ';') AS ST
WHERE
a.WFD_ID = {WFD_ID}

[/Code]

MVP
In reply to: Cezary Rzucidło

Interesting. We're currently reviewing the 2025 version, but we haven’t encountered this bug before. Could you possibly break down the issue into smaller steps?

At the end, you mentioned using the path with ID 2249, so I assume that’s a SQL command for the workflow control step. Maybe you could try comparing two rules to determine the correct path in the control step based on business rules?

Rule: Number of all child workflows
Rule: Positively finished subworkflows
Result: Choose either path one or path two.

I realize this may involve more work, but I believe it will simplify identifying the source of the problem in the incorrect workflow activity.

Using the SQL tracer, we identified the root of the issue. The queries within the IF statement are returning incorrect results. Specifically, the following query:

SELECT
COUNT(*)
FROM WFElements
WHERE WFD_WFDID = {WFD_ID}
AND WFD_DTYPEID = {DT:494}

returns 0 (zero), even when it shouldn’t. The same behavior is observed with the other query. This issue persists regardless of whether the queries are executed directly in the advanced settings window or invoked via a business rule. Interestingly, the same business rule works as expected when we log its value during a path transition.

MVP
In reply to: Adam Hatak

Dear Maks,
Thank you for sharing these ideas; they both look very promising.
Personally, I believe the simpler features also hold significant value, such as adding more content options on the application page—like text blocks, graphics, embedded elements, or HTML code.
These additions could enhance flexibility and improve user engagement.

I would also add to this the new possibilities for customizing the menu and the dashboard filters. Although the new way, from a dev perspective, may seem a little more confusing at first, it now allows for a much more intuitive and friendly UI/UX.

The new functionalities have added some complexity for the developers but much more flexibility for the customer's needs. It's way easier as a dev to screw it up, but if done properly the customer will end up with better results. We need to revise our internal development processes and practices now, but if we can offer more value, we don't mind.

Interesting. We're currently reviewing the 2025 version, but we haven’t encountered this bug before. Could you possibly break down the issue into smaller steps?

At the end, you mentioned using the path with ID 2249, so I assume that’s a SQL command for the workflow control step. Maybe you could try comparing two rules to determine the correct path in the control step based on business rules?

Rule: Number of all child workflows
Rule: Positively finished subworkflows
Result: Choose either path one or path two.

I realize this may involve more work, but I believe it will simplify identifying the source of the problem in the incorrect workflow activity.

MVP

Hi everyone! After upgrading to version 2025 we noticed that the Advanced settings are not working in the same way as they were in the previous versions. The query that was working just fine before is not doing its work. Does anyone else have the same experience?

If this helps, this is the query that we're using:

IF
(
/* Number of all child workflows */
SELECT
COUNT(*)
FROM WFElements
WHERE WFD_WFDID = {WFD_ID}
AND WFD_DTYPEID = {DT:494}
) = (
/* Number of positively finished subworkflows */
SELECT
COUNT(*)
FROM WFElements
WHERE WFD_WFDID = {WFD_ID}
AND WFD_DTYPEID = {DT:494}
AND WFD_StatusId = {WSTSPOSFINISHED}
)
BEGIN
SELECT {PH:2449}
END

MVP

Hi,
in a standard report, the number of items that a user sees is strictly related to the items to which he or she has permissions, minimally at the read level.
You can try, for example, to add a form rule which, after the user selects an item, e.g. from a given group, will automatically redirect him to, for example, the application/report page.
This will only be a workaround, because, for example, a more proficient user can, craft a link directly to the history of the item and read the data.

Sometimes I use a report/statement which is created using sql grid attribute, in the query you return only the data you want to show.
You can create a workflow with 1 step without paths. Remove all elements and leave only the grid, and possibly add attributes with which you could create filters for this 'report'.
The tile would lead right to this report.
You can also register and update a simple sub-circuit in parallel with the main workflow, containing only the data that people can see. and for this sub-circuit create a report for users, using the standard webcon report.

Regards.