Plumsail Workflow Action Pack activation issue

Workflow Actions Pack Microsoft 365 version
1

Hi,

I recently got the following error trying to activate the Plumsail Workflow Action Pack on a newly built site:

Publishing features are not enabled on the site.

Activating Plumsail used to work fine, I looked at one of our old sites and deactivated the feature, upon
attempting to reactivate it I got this error again.

Has anyone seen this before?

Thanks

2

Hello,

Please pay attention that you need to activate web application feature “Plumsail Auth Service”.

https://plumsail.com/docs/workflow-actions-pack/help-pages/Installation%20for%20SharePoint%202013.html#install

3

Thanks Roman,

How can I activate this in SharePoint Online? Do I need to deactivate and reactivate the solution?

Any idea why this has now failed? It worked ok previously.

Thanks

Alan

4

Alan,

Sorry, I didn’t notice this is SharePoint Online issue.

This is the hidden feature that should be activated on the site automatically.
Looks like in your case it wasn’t activated.
To fix it you can try to reactivate solution or activate the feature manually, as an example you can use the following javascript snippet via browser developer console (press F12 and navigate to console tab to open it):

[code](function(featureId, enable) {
var clientContext = new SP.ClientContext.get_current();
var featureGuid = new SP.Guid(’{’ + featureId + ‘}’);
var webFeatures = clientContext.get_site().get_features();

if (enable) {
    webFeatures.add(featureGuid, true, SP.FeatureDefinitionScope.site);
} else {
    webFeatures.remove(featureGuid, false);
}

clientContext.executeQueryAsync(
    function() { alert('Success!'); }
  , function(sender, args) {
      alert('Fail: ' + args.get_message() + '\n' + args.get_stackTrace());
});

})(’(function(featureId, enable) {
var clientContext = new SP.ClientContext.get_current();
var featureGuid = new SP.Guid(’{’ + featureId + ‘}’);
var webFeatures = clientContext.get_web().get_features();

if (enable) {
    webFeatures.add(featureGuid, true, SP.FeatureDefinitionScope.site);
} else {
    webFeatures.remove(featureGuid, false);
}

clientContext.executeQueryAsync(
    function() { alert('Success!'); }
  , function(sender, args) {
      alert('Fail: ' + args.get_message() + '\n' + args.get_stackTrace());
});

})(‘d7891031-e7f5-4734-8077-9189dd35551c’, true);’, true);[/code]

Please let me know if you need any help.

5

Thanks Roman,

I tried running that, however I got an Invalid or unexpected token error on line 17.

I can’t see what’s wrong (I don’t know the language at all), can you have a look for me please?

Thanks

Alan

6

Alan,

Could you please leave a request for screen sharing session at support@plumsail.com.

7

Hi Roman,

Thanks for all your help.

I deactivated the solution and reactivated it, then used the following (also using PnP-Powershell) to reactivate the feature on each site:

[code]$root = “https://domain.sharepoint.com/sites/rootsite”

Connect-PnPOnline -Url $root -Credentials $creds

$sites = Get-PnPSubWebs
Write-Host “Started at $(Get-date)” -ForegroundColor Green
foreach ($site in $sites){
$relativeurl = $site.ServerRelativeUrl.ToString()
$url = “https://domain.sharepoint.com$relativeurl”
Connect-PnPOnline -Url $url -Credentials $creds

Enable-PnPFeature -Identity d7891031-e7f5-4734-8077-9189dd35551c -Web $site -Sandboxed
Write-Host "Enabled on $url" -ForegroundColor Cyan

}

Write-Host “Ended at $(Get-Date)” -ForegroundColor Green[/code]

This appears to work fine, although I am confused why the solution stopped working - it was working fine a couple of weeks ago, with no changes made to the environment.

Thanks

Alan