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

latest posts

Hello all,

I'm not sure if this is something that changed in the versions or I'm missing any configuration.

I checked that users with the access 'Access and Edit all Instances' are allowed to select Available Paths even if they're not the assigned person.
I know that although having the rights to edit the instances, it couldn't be moved and that yellow message was shown because another person was the assignee. This is not happening in my processes and I'm not sure if that was something changed with the new releases or I'm missing any configuration.

I want a department to be able to check and edit instances but if they are assigned to another person, they cannot move the request to another step.

Did you faced something like that?
Thank you

MVP

Hi Jack,

there's an "old" way to achieve something similar.

Since I don't know the syntax I'm always using this approach:
1. Create a data row/table and activate the 'Functions' tab.
2. Select the correct hyperlink function.
3. Setup some dummy parameters
4. Click on show to see generated statement.

Afterwards I will modify the statement to fit my needs.

This should also work in the SQL data source.

Best regards,
Daniel

Hi everyone

I started using Webcon in May, so I'm pretty new to everything. I'm trying to setup an internal process to move and lock Active Directory users.
This involves moving the user to a different OU, but I can't seem to find this option in Webcon (other than executing Powershell which I'm trying to avoid for security reasons).
Does anyone have experience in this?

Greetings from Switzerland
Raymond

MVP
In reply to: Jack

yes, sure :-)
add this condition:

WHERE DATEPART(dw,DateData) NOT IN (1,7)

This is just an information:

WHERE DATEPART(dw,DateData) NOT IN (1,7)

The numbers of Sunday (1) and Saturday (7) may be different depending on the localization:
https://learn.microsoft.com/en-us/sql/t-sql/functions/datefirst-transact-sql?view=sql-server-ver16

Always make sure, whether they are the same on all your SQL servers or you will into unexpected errors. I speak from experience. :)