Can anyone suggest what is the best way to accomplish this ?
Scenario: Item fulfillment Record is being created by Shipstation Integration which has Package Content in Format A.
Requirement :
But We want to use that IF record to be exported to another application (Integration) and it mandates the IF record to be in a predefined format not same as Format A.
Please can anyone suggest what is the best possible way to achieve this ? If Suitescripting then which type would work the best.
A suitescript running on After Record Submit either under a user event script or workflow action script on the IF sounds like the way to go. It wants to only be triggered on the CREATE (not EDIT, unless you can post updates to your Shipstation integration).
This other question has an example of doing something after submission on an item fulfillment using the User Event Script.
Related
Hope someone can help me out here.
I've been working on updating/creating Script Deployment records via SuiteScript, and haven't been able to find a lot of information on it, so I've just been treating it like any other Record script.
(In Scheduled Script)
However, setting or updating the Schedule fields does not appear to work.
Regardless of any logic applied to those fields, no change is made and no system notes recorded.
Can someone help?
Many thanks!
Cheers, Giles
A quick look at the NetSuite Records Browser for the Script Deployment record shows that the schedule fields are not accessible via SuiteScript: https://www.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2021_1/script/record/scriptdeployment.html.
I have a request from the customer that they want every time they create a subsite (publishing site) .We have to add a custom column to OOTB Documents list.
I have done some researching the way to add the custom column to
Documents list in onet.xml but have no luck .
Then i think about the work around solution that i create a
ScriptBlock custom action that will call javascript function which
will add the custom column to document list , then i will put this
custom action to a feature ,and finally i will reference that feature
in onet.xml.
It run well but the javascript function call every time i refresh the page. I just want it run one time when i active the feature.
Does anyone have any suggestion ? I use sandbox solution and Sharepoint Online .Sorry for my bad English
I don't think a custom action is the right way to do this, Custom actions generally need some sort of user interaction.
Get CKS dev tools in Visual studio
Create a new SharePoint solution
Add a new web template(CKS Dev) to your solution from the Add new item menu in VS
Create an additional feature (web) with a list template (Your documents Library and add your column)
Update the Web templates onet file
Also sometimes it's better to put up what your having issues with as you have said you have had no luck with the above, What is the issue you are having, Post some code up etc rather than going down the route of changing the way you implement the solution
Many Thanks
Truez
I'm creating a fairly complex orchard form and need the results saved to a sql server database. From what I understand, I should be creating a workflow activity and then on form submit, connecting to the database and saving the data through C#. Is this the correct approach?
I could also just create a module which is my custom form, and build the form myself, but would like to take advantage of orchards forms.
My question is
1. Am I approaching this correctly? or is there an easier way to do this.
2. I haven't been able to find any documentation on creating custom workflow activities. Is this even possible to do? Can someone point me in the right direction.
No, the custom forms module already saves the results, you don't have to do anything more.
Yes, you can create custom activities. Look at the code for the existing activities for examples.
I need to learn how to build custom workflows in SharePoint. In addition to basic stuff like having legal sign-off on documents, I need to be able to execute arbitrary custom code at certain points. For example, after legal signs off it should export the document and update a database table indicating that a new version is ready.
Is this possible using SharePoint? If so, where can I find the documentation or tutorials I would need to get started?
Getting Started Link 1,Getting Started Link 2 links will help you to get started with the SharePoint Custom Workflows. And also it is possible to do any arbitrary code inside the workflow. Also there is another type of work flow called State machine for which there is a class one article
Workflow as the whole is built using sub parts called Activities which dictates what the workflow should do at a particular point of time, I remember you have an activity called Code Activity which will help you to achieve what you want.
Robert Shelton's Workflow Video Tutorial series is very helpful:
http://rshelton.com/Tags/Workflow/default.aspx
I am trying to implement a Workflow, where the user needs to select a destination document library.
I could figure out two possible ways:
Once the user manually starts the workflow, we would display a webpage where he would select the destination document library.
we would initially display a webpage. where User would select the destination.
After clicking a button the workflow would kick start.
Now for possibility "1":
How to redirect from a worlflow to a webpage. [tried Server.Transfer, but failed].
for Possibility "2":
How to start a workflow on button click.
Please also suggest which among the above 2 possibilities is a better solution.
What you need is a workflow initiation form. Exactly how you implement it and how much functionality can get will depend on the type of workflow you are working on, but you should be able to set up something to choose the destination.
I am assuming that you are talking about writing a workflow using Visual Studio. Personally, I would try creating a SharePoint designer workflow first to see if that meets your requirements.
In SharePoint Designer you can create an initiation form that accepts data from a user when they manually start the workflow. If the out of the box actions don't quite do what you need them to, you can create your own reusable custom workflow actions.