Hey @Webcon,
do you have any plans for this issue?
Hey @Webcon,
do you have any plans for this issue?
We've included your request into the backlog. I'm changing the status accordingly.
Hi,
I don't know when this was added/restored, but in version 2023.1.3.118 it's possible to right click a constant and select the other values from the group.
Best regards,
Daniel
We have just been using this unintended feature to conditionally execute a form rule. :)
We'll take this case under review to ensure the consistency of behavior throughout the system.
Hi Michal,
Thanks for your respond!
I understand concept of archiving in Webcon, I know that interaction is not possible.
What I am saying (point 2.) that after archiving, we loose read only privileges which were granted on instance level based on an attribute. This way we cannot control which archived instances should be visible for a group/user.
The other thing I mentioned (point 1.) , that today we do not have any control over form field visibility in archived instances, which imho would be useful.
Yes, we had the idea to keep these intances in Archived step or move to an other simpler workflow, but this way we would loose the main purpose to free up some storage space in active content db.
So a solution for at least to our privilege problem with archiving would be appreciated!
Hi Peter, archiving mechanisms were by design built this way to make them straightforward to use and simple to maintain in the product. At this point, we do not plan to extend their capabilities. On the other hand, since we can create multiple databases for processes (keep in mind we can store metadata and attachments separately), I think there should be sufficient options to manage storage efficiently. I'm sure our infrastructure experts will be able to suggest solutions accordingly.
Hi,
The idea is to always default to connections to the current database.
Now if we have defined others, some others are often substituted by default, which is irritating :)
Regards.
Hi Karol
Thank you for bringing up this suggestion.
Providing an easy way to provide a link to other systems (e.g. contacts in Dynamics 365) reminds me of the time when I used MatchPoint to configure applications in SharePoint.
For lookup fields there was a way to provide an url with a placeholder that had been replaced by the Id.
A similar approach could be used by WEBCON.
Apart from the suggested placeholders (id, appid, dbid), it would be great to choose whether the preview is available or not.
Hi,
In my opinion, the biggest advantage of BPS data sources is the ability to link to a selected element.
However, the disadvantage is much lower performance in advanced conditions, inability to join data, use union, and combine data from different content databases.
By changing the source from BPS to SQL, users lose the functionality of the link. Of course, we can achieve this in a different way, but it is not consistent, for example, with other pickers using a BPS source.
Would it be possible to introduce configuration options in the picker with an SQL source where we can map columns with ID, Appid, and dbid? Alternatively, a configuration where we return, for example, the entire constructed link (e.g., references to applications other than Webcon)?
In environments where we use several content databases, this would be very useful and would introduce greater consistency for users.
Regards.
Hi Michał,
Great to hear.
Meanwhile one of my Colleagues succeded to dedicate Global CSS (within BPS Studio) per template - using CSS selectors based on Template GUID from database.
Summing up - we got Global CSS part for all templates (shared) and dedicated section for CSS per template - based on CSS template guid selectrors.
Meanwhile we are excited to see revamp of User interface in WebCon BPS. And such CSS per template (exportable as well) would be great!
BR, Dominik
Hi Dominik,
are you using nested css rules this could help structuring the css.
Here's an example:
https://daniels-notes.de/posts/2024/graphical-cues#colorized-database-names
@Michał
I hope the decision will be to add uploading/referencing a .css file per template. :)
But we will see whether this wish will be fulfilled. :)
Best regards,
Daniel