- Create Site Action
- Get Parent Folder Action
- Create XML File Action
- HTTP-Request Action
- Query XML Action
- Query XML-File Action
- Set XML Action
- Update XML Document Action
- Call a Web Service Action
- Execute SQL Action
- Wait for External Data
- Regular Expression Actions
The source code is available too :-)
In further posts I will introduce each of the actions…
PS: I’m not a fun of SharePoint Designer Workflows. In almost every customer project I use Nintex Workflow!
14 comments:
NOSCOPE
the feature that you are trying to activate depends on other feature $Resources:FeatureTitle included in the solution 00000000-0000-0000-0000-000000000000, that is not installed.
That the error i got when trying to activate the feature in the site collection
Hi Alex,
during feature activation the site collection feature activates a hidden site collection feature. There's also a third feature with web application scope. All the features are in this single solution. Ensure that you have activate the web app feature on the corresponding web app. Do you use SharePoint Foundation or Server? I've only tested on SharePoint Server.
Bye, Christian
Hello
I am trying to use the Regex tool to convert a string like "24;#title" to simply "24".
Please can you advise on syntax?
Many thanks
The web app feature is activated.
the problem seems the hidden site collection feature. how can I solve this?
I am running SP server.
Regular Expression: use Extract Regex String with expression "^\\d*". You have to escape "\" with "\\"
Bye, Christian
@alex: Have you tried to reinstall? Which language you are using? I need more detailed information. Take a look at the ULS log to find more detailed information.
Bye, Christian
Solution Deployment : Global solution ilovesharepoint.workflow.activities.wsp, deployed to 0 servers. Deployment config object is null.
Updating SPPersistedObject SPEncryptedString Name=solution-deployment-ilovesharepoint.workflow.activities.wsp-0-85ba8348-d938-42dd-b589-ba64c33e58fe. Version: -1 Ensure: False, HashCode: 29396103, Id: d59a4551-14ab-4727-9db6-4124f6b50b1b, Stack:
at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()
at Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition.Update()
at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.CreateSolutionDeployTimerJob(DateTime dt, Collection`1 webApplications, SPSolutionDeploymentJobType jobType, Boolean globalInstallDlls, Boolean force, Boolean isRestore)
at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.CreateSolutionDeployTimerJob(DateTime dt, Collection`1 webApplications, SPSolutionDeploymentJobType jobType, Boolean globalInstallDlls, Boolean force)
at Microsoft.SharePoint.PowerShell.SPCmdletInstallSolution.InternalProcessRecord()
at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
at System.Management.Automation.CommandProcessorBase.DoExecute()
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
at System.Management.Automation.ScriptCommandProcessor.ExecuteWithCatch(ParseTreeNode ptn, Array inputToProcess)
at System.Management.Automation.ScriptCommandProcessor.RunClause(ParseTreeNode clause, Object dollarUnderbar, Object inputToProcess)
at System.Management.Automation.CommandProcessorBase.DoComplete()
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
at System.Management.Automation.Runspaces.PipelineThread.WorkerProc()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
That is the two errors present in the ULS, besides the error posted before when tryintg to activate form the Central admin.
With powershell no error visible, only what appears in the ULS.
tried to install several times, alwaysthe same outcome.
the feature you mentioned in the web app is already active.
letme know if you need more info
Hi Alex,
seems the installation fails. During the installation of the solution it will write to the farm's property bag (Config DB) of the farm. The installation will run under your current account. Check if you account has appropriate rights on SharePoint and the Config DB.
Bye, Christian
Chris I am using an account with farm admin rights.
I have installed others solution without problems (I am already using your lookup column)
@Alex: Has this account admin rights on the server?
The account is local admin for the 3 servers on the farm.
alexandros.darius@gmail.com if you want to contact me directly with other questions.
After checking the permissions of the account in the database, i found that it had no permission despite being the account used as farm admin.
So I run it again in powershell using the account with permission to access the config DB and it installed successfully.
Thanks for the Help!
For the error:
NOSCOPE
the feature that you are trying to activate depends on other feature $Resources:FeatureTitle included in the solution 00000000-0000-0000-0000-000000000000, that is not installed.
My permissions were ok, but it wasn't until I used the -force switch on the Install-SPSolution that it started working. Note - this did take my site totally offline for a few seconds.
any advice on using the regex extract string action to pull from the begininng of a string up to the first pipe "|" ?
Post a Comment