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

latest posts

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.

I have created a special report for a subdevision, and granted a User for only see the Report.
But he does not have the grant to look into the Workflow.

It ist our internal Ticket system and only the IT Guys shoud get access to the Workflow and Ticketdatas
Other Subs only should have their own Report to see how many Tickets are in work. And this overview shoud be only visible to the Sub Manager.

So i granted the Process to the User and the Report to the User.
He see the Process and see the Report, but when he open the Report, there is no dataset in it.
When i granted me personaly to the Report i can see the Datasets.

Have i think the wrong way?
How can i made that the Manager can see the Datasets only in the Report but coudn´t access to the Workflows and to the rest of the datas?

Greets
Andreas B.

Hello everyone,

I have a workflow where I generate an attachment. When I create the attachment on my path the next step is that, a OneDrive connection is established in the next step on entry using the "Start editing a file using OneDrive" action. In my workflow, about 200 people are authorized to use it. From what I see now, this action grants each person read and write permissions. Essentially, it works, but I’m experiencing extremely long loading times of up to 30 seconds. Is there any way to configure this differently or improve the setup? Does anyone have any ideas on how I can reduce the loading times? I would be grateful for every single tip.

MVP
In reply to: MANSOFT

I mostly agree. I feel almost the same way.

PS.
Customer voice.... || wall || Partner || wall || Software manufacturer with a thousand walls along the way ... :) that's all on the subject

I will also only add one comment, because I asked someone via LinkedIn, what's his opinion:

Quote: "
My Boss is delighted, i updated my personal dev
a lot more possibilities to create more modern start pages for apps

like it also as we all working on office365 and design is familiar
i showed it to my friend and he told me that it looks almost like dynamics 365 :)

"

@All
After Mansoft and I went off topic, please focus on Maks question. :)

In reply to: Daniel Krüger (Cosmo Consult)

I'm sorry that I did not get across the reason, why I used "objective".
I used this word, not because we are a partner, because we already spend hours to modify the UI because we received numerous negative feedback. So, I used "objective" in quotes from a quantity perspective.

That's the only reason I used this word. Even if this my sound strange, but I wouldn't have minded keeping the old "UI" alive. I'm more focused on functionality than "looking pretty". Which I heard complains about more often than not. :)

I'm also experimenting with a "full screen" functionality at the moment because I don't like how much space get's lost, which I also voiced using another communication channel. So, yes while I'm definitely biased I also point out flaws or things I don't understand.

Quote from my blog post about the change log of 2025:
New Workflow designer
"Hidden no longer means hidden :( At least in this version, let’s cross our fingers."

While I agree with some of the mentioned issues, I haven't verified others, at some point a version needs to be released. This is also something everyone of us here propagates when building new processes/applications. Create the first working version, and build up on it afterwards.

Off topic:
I have the feeling that suggestions from customers are more likely to be heard than those of partners. We don't pay the bill. This is also something I voiced in some discussions and I never got a response. So I may be right. :)

I mostly agree. I feel almost the same way.

PS.
Customer voice.... || wall || Partner || wall || Software manufacturer with a thousand walls along the way ... :) that's all on the subject

MVP
In reply to: MANSOFT

I don't know why your opinion should be more objective than mine. IMO. For each of us both opinions are subjective (and mine is additionally not dictated only by the end user, as a non-partner you can maintain and administer this system for end users and often do so to a much greater extent than partners within strictly defined provisions of agreements) but never mind that.

I am open to changes but from a product like WEBCON I expect above all:
- stability
- bug free (if possible)
- a proven and TESTED product and not a product given to the user or partner to look for errors in accordance with... they will report it to us then we will fix it, we will cut costs and we will not attach too much importance to quality.
- maintaining some minimum compatibility (I really don't like the action with themes - we changed the theme, we informed you and accept it or take the costs of its correction and improvement as part of our update). Theme is just one example of how certain "costs" are passed on to the customer as part of "ensuring updates" that the customer already pays for.

Let's not kid ourselves, the product is not cheap, the product is quite good overall, but the larger the corporation and the more customers, the worse it treats them and the product itself.

Critical opinion, but I know my own stuff and not only based on experience with webcon.
You can also introduce changes in smaller steps but refine them more. Here we have rather a total overturning of the table.


Update (thought):
I assume that as an mvp you have a somewhat limited scope for negative statements on the subject of WEBCON.

Besides, I also know perfectly well what the provisions of partnership agreements are. So if you want to talk about the OBJECTIVITY of your statements in relation to mine, it looks bad against the background of your profile :]

PS. Of course, full respect for your knowledge and experience as well as the help you provide, without which I would have failed many times :)

I'm sorry that I did not get across the reason, why I used "objective".
I used this word, not because we are a partner, because we already spend hours to modify the UI because we received numerous negative feedback. So, I used "objective" in quotes from a quantity perspective.

That's the only reason I used this word. Even if this my sound strange, but I wouldn't have minded keeping the old "UI" alive. I'm more focused on functionality than "looking pretty". Which I heard complains about more often than not. :)

I'm also experimenting with a "full screen" functionality at the moment because I don't like how much space get's lost, which I also voiced using another communication channel. So, yes while I'm definitely biased I also point out flaws or things I don't understand.

Quote from my blog post about the change log of 2025:
New Workflow designer
"Hidden no longer means hidden :( At least in this version, let’s cross our fingers."

While I agree with some of the mentioned issues, I haven't verified others, at some point a version needs to be released. This is also something everyone of us here propagates when building new processes/applications. Create the first working version, and build up on it afterwards.

Off topic:
I have the feeling that suggestions from customers are more likely to be heard than those of partners. We don't pay the bill. This is also something I voiced in some discussions and I never got a response. So I may be right. :)

In reply to: MANSOFT

I don't know why your opinion should be more objective than mine. IMO. For each of us both opinions are subjective (and mine is additionally not dictated only by the end user, as a non-partner you can maintain and administer this system for end users and often do so to a much greater extent than partners within strictly defined provisions of agreements) but never mind that.

I am open to changes but from a product like WEBCON I expect above all:
- stability
- bug free (if possible)
- a proven and TESTED product and not a product given to the user or partner to look for errors in accordance with... they will report it to us then we will fix it, we will cut costs and we will not attach too much importance to quality.
- maintaining some minimum compatibility (I really don't like the action with themes - we changed the theme, we informed you and accept it or take the costs of its correction and improvement as part of our update). Theme is just one example of how certain "costs" are passed on to the customer as part of "ensuring updates" that the customer already pays for.

Let's not kid ourselves, the product is not cheap, the product is quite good overall, but the larger the corporation and the more customers, the worse it treats them and the product itself.

Critical opinion, but I know my own stuff and not only based on experience with webcon.
You can also introduce changes in smaller steps but refine them more. Here we have rather a total overturning of the table.


Update (thought):
I assume that as an mvp you have a somewhat limited scope for negative statements on the subject of WEBCON.

Besides, I also know perfectly well what the provisions of partnership agreements are. So if you want to talk about the OBJECTIVITY of your statements in relation to mine, it looks bad against the background of your profile :]

PS. Of course, full respect for your knowledge and experience as well as the help you provide, without which I would have failed many times :)

https://www.youtube.com/playlist?list=PL-xscdmsg7YonDzQM-9Aix0Yfzak5LlN1
(for the new version there is no, so the manufacturer includes instructional materials in the new 2025 version referring to the old version and the old interface... great!)

When I look at these fresh (3m) video materials and the current version, it brings tears to my eyes how this interface was screwed up in the new version..
It was so clean, clear, CLEAR, subdued, refined to the smallest detail. From a distance, you could tell what was where and how

Remember, most people are visual and "buy" with their eyes.
I personally don't know how to work with the new interface because it hurts the eyes regardless of the dark/light theme.


So I'm looking through this and thinking to myself that, damn it, they could have made a theme based on the new UI components with the name WEBCON (OLD) 2024 and at least kept the component colors as consistent as possible with the previous release.

In reply to: Daniel Krüger (Cosmo Consult)

If I have to name one favorite than it's the form rules to determine the visibility of item list row actions, while the phases and actors are just behind.

But it's really hard there are many interesting changes.
Therefore I put together an "excerpt" which is of course subjective. :)
https://daniels-notes.de/posts/2024/webcon-bps-2025-change-log


@Mansoft
The first version of anything will always have some flaws, but we need to start somewhere. Of course, you are free to wait until those are addressed, but if you don't want to mention them, then some of those may get unnoticed and they will still be there, when you test it the next time.

But I have to comment on this "You've put your fingers in something you shouldn't have changed. You don't change a good horse when it's winning."
This is your subjective impression as a WEBCON user. As a partner I can offer a little more "objective" feedback. During the last year we got a regular comments regarding the (out)dated UI. This even forced us to create our own theme, which we can now get rid of / need to review. Yes, existing users will have to get comfortable with the new UI and I agree that a the screen "real estate" has been reduced even further, but a change had to come. At some point you need to switch to a fresh horse, even if it hasn't has any race experience yet. The old one was slowly but steadily dying.

I don't know why your opinion should be more objective than mine. IMO. For each of us both opinions are subjective (and mine is additionally not dictated only by the end user, as a non-partner you can maintain and administer this system for end users and often do so to a much greater extent than partners within strictly defined provisions of agreements) but never mind that.

I am open to changes but from a product like WEBCON I expect above all:
- stability
- bug free (if possible)
- a proven and TESTED product and not a product given to the user or partner to look for errors in accordance with... they will report it to us then we will fix it, we will cut costs and we will not attach too much importance to quality.
- maintaining some minimum compatibility (I really don't like the action with themes - we changed the theme, we informed you and accept it or take the costs of its correction and improvement as part of our update). Theme is just one example of how certain "costs" are passed on to the customer as part of "ensuring updates" that the customer already pays for.

Let's not kid ourselves, the product is not cheap, the product is quite good overall, but the larger the corporation and the more customers, the worse it treats them and the product itself.

Critical opinion, but I know my own stuff and not only based on experience with webcon.
You can also introduce changes in smaller steps but refine them more. Here we have rather a total overturning of the table.


Update (thought):
I assume that as an mvp you have a somewhat limited scope for negative statements on the subject of WEBCON.

Besides, I also know perfectly well what the provisions of partnership agreements are. So if you want to talk about the OBJECTIVITY of your statements in relation to mine, it looks bad against the background of your profile :]

PS. Of course, full respect for your knowledge and experience as well as the help you provide, without which I would have failed many times :)

MVP

If I have to name one favorite than it's the form rules to determine the visibility of item list row actions, while the phases and actors are just behind.

But it's really hard there are many interesting changes.
Therefore I put together an "excerpt" which is of course subjective. :)
https://daniels-notes.de/posts/2024/webcon-bps-2025-change-log


@Mansoft
The first version of anything will always have some flaws, but we need to start somewhere. Of course, you are free to wait until those are addressed, but if you don't want to mention them, then some of those may get unnoticed and they will still be there, when you test it the next time.

But I have to comment on this "You've put your fingers in something you shouldn't have changed. You don't change a good horse when it's winning."
This is your subjective impression as a WEBCON user. As a partner I can offer a little more "objective" feedback. During the last year we got a regular comments regarding the (out)dated UI. This even forced us to create our own theme, which we can now get rid of / need to review. Yes, existing users will have to get comfortable with the new UI and I agree that a the screen "real estate" has been reduced even further, but a change had to come. At some point you need to switch to a fresh horse, even if it hasn't has any race experience yet. The old one was slowly but steadily dying.