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

latest posts

In reply to: Łukasz Zientek

Are you sure you are starting a new document with this account?

I created a scheduler where I have a template of the element.
On timeout every week I would like to create a new element.
I override the owner but still the license is required.

From my perspective it looks like a bug.
99% of customers have dedicated accounts for bps_svc and bps_appPool and now if a customer used all licenses I'm not able to do that.

Btw I found another example: if you have 10 API integration you have to have extra 10 licenses...

MVP

As 2025 version have been released, we've got a new changelog to read through: https://webcon.com/wp-content/uploads/2024/11/Changelog_2025_1_1_23_EN.pdf

What are your thoughts on changes? Which ones are yours favourite? :)

For me - ALL TRUE, and ANY TRUE operators sounds great! So many nested boolean logic to update ;)

MVP

Hi Łukasz,

based on your description I'm assuming that the assembly has not been signed before.

I would check:
- that the configuration defines the correct assembly for the action. The one in which all the actions/business rules etc. of this plug-in are defined.
- Create a new action using the current version. Maybe the XML contains outdated information.


Best regards,
Daniel

Good morning,

After updating BPS to version 2023.1.3.240, we encountered an issue in our production environment.

The problem concerns an SDK add-in that enables sending XML data to MSMQ queues. We needed to update this add-in because, starting with version 2023, the methods were changed to asynchronous. The add-in relies on an external DLL file, Experimental.System.Messaging.

To include this DLL in the add-in, I had to sign it with a strong key. According to BPS, everything went smoothly—the package was implemented successfully, and the add-in functions correctly when the user proceeds through the path.
However, the issue arises when the document follows a path triggered by a global action.
In this case, the add-in generates the following error:

Could not load file or assembly 'Experimental.System.Messaging, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044) File name: 'Experimental.System.Messaging, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null'

It seems that, in this scenario, the add-in does not recognize that the DLL file is signed with a strong key. Has anyone encountered a similar issue?