Basically I want the orders to import under Pending Fulfillment only when the selected triggering client field has a value in it (any value). If it is blank I don't want this workflow to run on that SO. I have another workflow in place that affects other orders that are imported through Web Services, so this will be just for specific orders when the Triggering Client Field has a value. I set it up, as you can see in the images attached and no luck!
Parameters: Order Status=Pending Fulfillment (Static value)
Trigger on: After Field Sourcing
Contexts: Web Services
Triggering Client Fields: Custom free form text field that will be
populated with a 4-5 digit number
This looks like it will only work within the UI when someone is entering a sales order - and actually it won't work at all because if that's a free form text field, then it won't trigger the "After Field Sourcing" event. I would make the trigger Before Record Submit, or After Record Submit instead, and then under the "Condition" section, use the visual builder to tell set the criteria to only when Handshake Order ID is not empty. That should do the trick for you.
Please change your workflow action as below
Workflow Action : Import Status
Trigger On : Entry
Condition : {custbody11} is not null
Related
We are currently implementing Azure Devops for our backlog and task management. We are using a Kanban board setup. I would like to add a query to our dashboard to show Stale actions, effectively I want to see a list tasks that have been assigned but not modified in 7 days.
Initially I tried the state change date, but am finding that some tasks are having activity but just not a state change.
So I tried Changed Date, but that shows changes to the priority level when other items are changed.
How can I write a query that would only identify work items that have not been modified in over 7 days?
Currently there are no existing field can meet your requirement. And the Changed Date field will be updated if there are any changes to this work item as you mentioned.
As a workaround, you could try following steps.
Add a custom field to a work item type (Inheritance process), I add field LastEdit which is Date/Time type and IsActive which is Text (single line) type for Task, and field IsActive is required, as below.
Add a rule to a work item type (Inheritance process), I add 3 rules for Task, as below.
Therefore, the field LastEdit is the last edit time, and users must edit the field IsActive when they update this work item and then the field LastEdit will be updated, otherwise they cannot save their changes.
Now you could filter target Tasks that using the field LastEdit, as below.
Here's the approach I tried utilizing rules to set a "LastEdit" custom date field. I have 4 of these set for different changes, then I can query off the LastEdit date. It'll take a few days before I know if this works or not, but some simple testing seem ok. The major shortcoming I see is that I cant create a rule to update the LastEdit based on a new comment being entered.
How can we notify a user to select a value to a drop-down field in Azure DevOps work item without making it a required field.
The reason of not making it mandatory is because it is not a compulsory information.
But the reason for this 'way to notify' is to make sure that this value is to be filled when it is relevant (which is most of the time - but not all the time).
There is no option to add a notification on a field without making it mandatory, but there is a workaround to force the user to think about the value of the field.
You can add an additional boolean field who is enabled by default. This field can be used to create a rule for your original field, to indicate if it is required or not.
So to set this up you have to add the following fields/rules to your work item type:
2 fields:
originalFieldName (the field with extra attention)
booleanFieldName (Boolean, default value: true)
2 Rules:
When a work item is created
Then set the value of booleanFieldName to 1
When the value of booleanFieldName Equals 1
Then make originalFieldName required
With this solution the user always have to fill in the field or make the field is optional by deselecting the boolean field.
If you just want a message to be displayed in the work item to notify user to select a value. There is a workaround that you can create a customized process. You can customize the fields and pages in the your custom process.
For testing, i create a custom process and add a notification text to a group name to indicate use to select a value for a field. Please refer to below step.
1, Go to the Process section in the Organization Settings, and select the process that you want your custom process inherit from.
2, Then choose the work item type you want to edit. You can edit or add a fields or group to the work item type. For below example, i edit the title for Planning group to add a notification message.
For more information about custom process please refer the official documents.
If you already choose a process to your project. You can refer the detailed steps here to change your project process to the customized process.
Hope you find above helpful.
I need help on how to create the following workflow please. I added a new body field in the NetSuite sand box called “sow.” It is a check box field and I added it to the sales order transaction page. Is it possible to make a formula that says: If “contract type” field that exists on opportunity equals “sow”, check box, if not don’t check box? So the field contract type is on the opportunity and once this is contract type is set to SOW the checkbox SOW on the opportunity should be checked.
Your workflow will need a single State. The State will have a single Set Field Value Action, which will mark the checkbox accordingly. This Action will have a Condition that looks at the value of the Contract Type field.
New Workflow
Name the Workflow
Give it an ID
Record Type: Transaction
Sub Types: Sales Order
Trigger Ttype: Before Record Load
WorkFlow Condition: Condition
Field: SOW -- Compare Type: checked
Workflow Condition
I'm starting to get the hang of NetSuite but this one has stumped me. I am looking for a way to update the line items on an order from a workflow in NetSuite. From what I can tell it doesn't seem to expose those fields, is there any way around this?
I have a saved search returning all of the transaction line items that I want modified, there is a field on the Sales Order Line Item called "Create Fulfillment Order". It shows up under saved searches as "Create Fulfillment Order Column", but when I add an action to a workflow to set the field value, the only fields that show up are Sales Order fields. Is there any way to access the Sales Order Column fields, since that's really what's being returned by my saved search anyways.
I've looked at the Sub Types defined in the workflow to see if there's one for Sales Order Item or anything but there's not, just Sales Order. Any help would be greatly appreciated, thanks in advance!
There's nothing built-in that will let you access transaction line items from a workflow. You'll need to use SuiteScript to create a custom workflow action. Then you can call that action from your workflow.
Suppose I have two objects
1.Account- standard object[it has a field name Status_c which is a picklist having value inprogress and closed]
2.Client_c - custom object[it also have same field name Status__c which is a picklist having value inprogress and closed]
and Client__c has lookup to Account name which means Account has a related list of client object .
My question is :
I want to write a trigger where if I put account status to "closed" I can not put client status to "closed",it should throw an error message on client object or if I put client status to closed I can not put account status to closed vice versa.
Can any one please help me to write a trigger on this??
Conceptually, I think what you are looking to do is set up Validation Rules on both of those objects. Your validation rule on Client_c should be pretty simple: TEXT(Status_c) == 'Closed' && TEXT(Account_c.Status_c) == 'Closed'
The more interesting piece is how you handle making sure none of your related items are Closed when you move the Account to Closed. I tend to prefer creating a field on the Account that keeps track of the status of the related items (checkbox) that basically tells me whether it is valid for me to change my status or not. In this case, the validation rule becomes pretty simple. In order to set that boolean value, I end up using a Trigger on Client__c that basically just grabs all the Accounts when a Client is being modified in the batch (taking into account both inserts, upserts, and deletes):
SELECT Account__c.Id FROM Client__c WHERE Id =: Trigger.new OR Id =: Trigger.old
Then create a Set of all the Account Ids (in this example, named accounts), and run a query to retrieve ALL Clients related to those Ids (in a single query to ensure you don't hit SOQL limits).
SELECT Account__c.Id, Status__c FROM Client__c WHERE Account__c.Id =: accounts
From the results of this, you will iterate over all of the entries, tossing them into a Map keyed by the Account Id where the value is a List of Clients. When you are done, run a query to get all accounts based on the "accounts" list from earlier (which was just a list of strings, not actual Accounts), subsequently iterate over all the Clients associated with that Account, and if a Client is marked as Closed, you will update the metadata of that Account accordingly. If no Clients are closed, the Account will be marked as such. Once you are finished, run an update statement to update the list of Accounts that you have modified.