I am working on WCF WorkFlow Service Application. i have two ReceiveAndSendReply Activity in sequence. i have set CanCreateInstance to true in both the activities Now i am not able to access the second ReceiveAndSendReply Activity. i know this because its needs to be executed sequentially right ? then how can i create WCF service methods in such way that i can call any of the method anytime.i think that can be achieved by creating State Machine Workflow but how to create in WCF WorkFlow Please suggest me some best ways i can do this.
You can put ReceiveAndSendReply in a pick branch. You can have several branches with several ReceiveAndSendReply activities. But if you have more service calls to your workflow then the recommended way is to use state machine.
Create a parallel activity and add one branch for every receiveandSend activity and set its CanCreateInstance to true
Related
In the use of Argo Workflows, we have a scenario to call the existing microservices. We can make an HTTP call through a script, but this method creates a new pod each time, which takes a long time. Wanted to know if it's good practice to do that and what would be the best way to do that?
An Argo Workflow will always create at least one pod. You're right that this is probably excessive if the only purpose of your Workflow is to make an HTTP call.
For something lighter-weight, check out Argo Events. You can configure an EventSource, choosing from a wide variety of input sources hopefully building something very similar to whatever you're using to kick off the Argo Workflow. Then you can configure a Trigger to make an HTTP call.
Feature cycle time is a very important metric, but in ADO there doesn't seem to be a way to get the State of a Feature to automatically update when the first story moves into Active (or the last child is closed). Does anyone know of a way to have this happen?
No, that will never happen. This area for custom application and solutions. You can try the following:
TFS Aggregator
Write your own solution through rest api: Automation of state changing for Azure DevOps work items based on states of child work items
Use additional solutions: Automation of state changing with Azure Logic App
I want to create change request using scripts and not from the GUI page. How can I achieve that ? Also, there is a single sign on check of my organization too.
A few options:-
Create Scripted REST API - this exposes a URL which can be called by an external system. Tricky if you are new to SN.
As #Rafay suggestions - setup a scheduled event. Check out https://community.servicenow.com/community?id=community_question&sys_id=b32c0765db9cdbc01dcaf3231f961984
Scheduled events can be scripted/reports or create templates.
Templates can create of tasks without any coding - may be easier if it meets your requirements? These are referred to as templates and can be created via the UI then scheduled to create them (e.g. A regular server patching activity).
This has happend to me more than once, thought someone can give some insight.
I have worked on multiple projects where my project depends on external service. When I have to run the application locally, i would need that service to be up. But sometimes I would be coding to the next version of their service which may not be ready.
So the question is, is there already a way that can have a mock service up and running that i could configure with some request and responses?
For example, lets say that I have a local application that needs to make a rest call to some other service outside to obtain some data. E.g, say, for given a user, i need to find all pending shipments which would come from other service. But I dont have access to that service.
In order to run my application, i need a working external service but I dont have access to it in my environment. Is there a better way rather than having to create a fake service?
You should separate the communications concerns from your business logic (something I call "Edge Component" see here and here).
For one it will let you test the business logic by itself. It will also give you the opportunity to rethink the temporal coupling you currently have. e.g. you may want the layer that handle communications to pre-fetch, cache etc. data from other services so that you will also have more resilient services at run time
Our org is planning on basing parts of our business model on the premise of recurring workflows in CRM 2011. However, we sometimes run into an issue with a backed up workflow queue, or for some reason need to restart the server (update rollups, etc.), or in some other way find we have to restart the CRM's async service.
What would happen to any workflows in the "waiting" phase in this scenario?
I see the workflow in the AsyncOperationBase table with the "waiting" statuscode; when the service comes back online, does it look at this table and resume accordingly?
In the above scenario, what what would happen if the service was stopped, and in the interim, the workflow reached its PostponeUntil date? Does the service look at all non-complete future and backdated workflows and decide what to with each? Or does the workflow just fail altogether?
Any fails in the process would obviously be a deal breaker for this element of the CRM system, and we'd have to develop an external component to handle recurring items.
I'd expect there to be some documentation on this, but I can only guess that the WaitSubscription class has something to do with this topic, but it's for the most part undocumented.
For now, we've decided to go with an external service to manage this, due to the seemingly black box nature of the async process. Tracing the calls to the database server does show a lot of calls to the AsyncOperationBase table, which tends to make me believe the service always checks to see if a job is being done, but in the absence of extreme testing, for now it's more secure to use a separate service for this requirement.