The above approach is still problematic though. The file will obviously be lost every time we do a clean install or we upgrade / reinstall the node module. Obviously this is not acceptable from a DevOps perspective. Any ideas on how to address this? All configuration changes should reside within the solution, not in external modules and dependencies.
Please ignore the above response. We were looking at the incorrect abp.js file.
The correct abp.js file is in the abp-web-resources node module.
After amending the line it works as expected
Hi
We are having the same issue however, The only reason I am reviving the thread is because in our version of the application (11.2.1 MVC & Jquery) does not have the line abp.multiTenancy.tenantIdCookieName in the abp.js file.
When we implement the Configuration.MultiTenancy.TenantIdResolveKey update the API works with cloudflare but it breaks the impersonation feature.
Is there anything specific to our version that we should be doing?
Hi @ismcagdas
This is great news, thank you!
We are running on ASP.NET CORE MVC & jQuery and will try to adapt from the article for ASP.NET Zero's Angular version. Anything in particular you feel we should consider in this case?
Just a note that the link in the article to the ElsaDemo github repo gives a 404 error, you might want to just review that.
Hi @mightyit,
Thank you for bringing up your concerns regarding Elsa's integration. We value your feedback and understand the importance of having a robust workflow capability for your organization and others.
We apologize for the oversight in not explicitly addressing the Elsa integration in our current roadmap. Rest assured, we are committed to continuously improving our product to meet your needs. After considering your feedback, we will prioritize discussions around incorporating Elsa into our upcoming milestones.
Thank you once again for your valuable input.
Hi there, Support Team!
We were just hoping to get some feedback since you stated about a month ago that you would prioritise discussions around Elsa's integration into your upcoming milestones. Will this be addressed in a future milestone, and when do you expect this to occur?
Sorry for the persistence on this issue, but we also need to make decisions about the future direction of our systems.
Kind regards
Hello @ismcagdas,
I felt compelled to mention that our company shares a deep interest in ensuring a seamless integration of AspNetZero and Elsa core.
Most business systems require long-running workflows and business rule engines as a key feature. Therefore, having a robust and enriched workflow capability holds immense importance for various organisations, including ours.
We have taken a comprehensive look at your roadmap for core and jquery. In our perspective, it holds greater importance than aspects such as coupon features, error messages via email (considering the wide availability of excellent third-party alternatives), or menu item ordering, a problem we've already found a solution to. Our concern lies in the absence of any explicit commitment towards addressing issues concerning Elsa integration on a permanent basis. In my humble opinion, this could be a significant oversight.
We, therefore, respectfully request you to prioritize this issue, as we believe the matters related to Elsa are not being given the necessary urgency and attention they truly deserve.
Hi @mightyit,
We are planning to publish a blog about Elsa and update the docs as soon as possible.
Hi @m.aliozkaya
Are there any updates to this?
Kind regards
Thank you for the response.
The integration with Elsa was a key factor in our decision to use ASP.NET Zero, and we are eagerly anticipating the updated documentation to proceed with a feature development plan that heavily relies on utilizing Elsa within the framework. Our project timeline and deliverables are dependent on the availability of these resources.
Given the criticality of this feature to our project, I kindly request that you provide me with a more specific estimated time of arrival (ETA) for the updated documentation. This will enable us to effectively plan our development efforts and allocate resources accordingly.
I understand that unforeseen challenges can arise, but having a general timeframe or a rough estimate would greatly assist us in managing expectations internally and communicating with our stakeholders.
Product Version: 11.1 Product Type: MVC + Jquery Framework: .Net Core
I am trying to integrate with Elsa in our solution. However I have come across a few problems and cannot seem to make it work. I believe this is due to the fact that the guide and demo project are outdated. The guide and demo project are for .Net 5 and the Elsa packages are version 2.0.0.159.
I cannot due to various package dependencies use the Elsa packages of that version in our solution. The earliest version I am able to use is 2.5.0. Elsa has made some changes to their solution and packages since 2.0.0.159 most notably to the Webhook Definitions List class which is required according to the documentation to register Elsa controllers in the Asp Net Zero dependency injection system.
The class has now been moved to a different package: Elsa.Webhooks.Api I made the adjustment to the Initialize method in the WebMvcModule
This is how the workflow page looks
and there are errors in the console
This is what my Program.cs looks like
It seems like either the controllers and razor pages aren't being registered correctly due to some difference between the demo/documentation elsa package versions and the version I am trying to use, or the embedded static files are not being loaded correctly.
Has anyone managed to get the elsa integration working on .Net 6? If so how were you able to get it to work?
Any help would be appreciated.
Hi
we managed to solve the issue after reading this https://support.aspnetzero.com/QA/Questions/10764/Bad-performance-due-to-AbpUserTokens-table
