Question

Business processes not available after migrating to production

Version 9 Workflow

Updated May 6, 2015

asked on May 5, 2015 • Show version history

I exported (as .wfi) and imported two business processes and two workflows from a Test environment to Production. I reset the connection profile using the wizard, validated and published them. Everything seems normal, except:

-When I right click on a folder in Production and select 'Start Business process' none are available. Usually they are greyed out if they are not active from the selected folder, but these are not there.

- Under the 'Commands' window of toolbar customization the Category for Business Processes is missing.

- In the Designer my group can Start and View the BP starting rule, but if I try to edit the rule using Windows authentication, I get permission denied. Yet I can edit the workflow starting processes.

I must be missing something very simple, but I can't see what it is. I've successfully done this in the past.

1 0

Answer

SELECTED ANSWER

replied on May 6, 2015

Resolution: I enabled the Business Process Option "Display This Business Process's Information".

I disabled this when developing the workflows because I don't need business process functionality such as displaying statuses / instructions. (I just wanted workflows that start with a toolbar icon.) It appears that when you initially publish workflows with this setting off it also suppresses the display of the business process in the UI so that you can't see it to start it. Once I enabled and published, I could see the processes under Tasks/Start Business Process. Then you can disable, republish and they stay visible.

0 0

Replies

replied on May 5, 2015

Beyond the Workflow Connection profile there is a Business Process Profile.

I'm guessing this is still pointing to your Test environment.

A workflow can be on a production environment, validated, tested, and everything work but the business process still be linked to the dev environment. Thus, when right clicking on an entry you won't have it listed as an available BP since this is polling the BP's on the Production server.

Change this option and you should be good to go.

2 0

replied on May 5, 2015

Thanks for the update. I checked those parameters and they're pointed at Production, although I don't think I had to do that manually, it must have happened with the import wizard. So that doesn't seem to be causing my problem. The fact that I can't login to edit the starting rules is strange.

0 0

View 2 previous replies

replied on May 5, 2015

The Workflow Server itself has security based on Windows authentication. By default local administrators on the Workflow Server get access to everything. Is it possible that you're not an administrator on the Production server? Or that security for the Production server has been configured differently?

0 0

replied on May 5, 2015

Miruna, are you saying I have to be a Windows administrator on the workflow server in order to edit starting rules for a business process?

0 0

replied on May 5, 2015

Thinking about it, that doesn't seem to be the issue because I've successfully published an updated business process to the existing repository. I really don't know what I'm doing different this time other than it being to a brand new repository.

0 0

replied on May 5, 2015

When you edit business process starting rules, you are prompted to log into the repository. The dialog defaults it to Windows authentication. Is it possible that your domain user account is not set up to log into this new repository? Can you log into it from the Client with Windows authentication?

1 0

replied on May 6, 2015

Yes, Windows authentication works for the client.

0 0

replied on May 5, 2015

I think the answer may in the Workflow Console - the repository I'm importing to is not listed under:

Server Configuration/Repositories

But when I try to attach the new repository to the Production server all it brings up is a window showing the repository I'm already attached to, with no way to change it.

0 0

View 5 previous replies

replied on May 5, 2015

Business Processes do not required that the repository be attached to the Workflow Subscriber.

0 0

replied on May 5, 2015

But what about for my 2 workflows?

0 0

replied on May 5, 2015

The subscriber is in charge of evaluating starting rules and wait conditions. It's not clear to me which repositories and servers we're talking about in this sub-thread. Is this a new Production server that's not been configured with repositories?

0 0

replied on May 5, 2015

Today I imported two new workflows and two new business processes into a new repository on an existing production server. The new repository has not been put into production yet. That's where I don't see the business processes, and the workflows aren't starting.

On the same production server we have a second repository that has been in use for two years, and into which I have successfully migrated a business process. That's why I'm thinking my server rights are not part of the issue.

(Sorry, I didn't see the previous answer before I started this. You can just ignore the previous thread. )

0 0

replied on May 6, 2015 • Show version history

Ah, has the brand new repository been configured to have workflow listen to it yet?

Using workflow administration console is it listed under the Server Configuration -> Repositories node?

It sounds like a workflow subscriber isn't listening to your brand new repository. (Which is what Miruna is getting at)

0 0

replied on May 6, 2015 • Show version history

I have now got that configured, where I could not previously. The problem was like Miruna said, my windows account couldn't add it but another account (the laserfiche workflow user) could. (I don't understand why -- since I have all the same Laserfiche rights as the workflow account. )

Unfortunately, this hasn't fixed the problem. I still can't use Windows authentication to access starting rules of the Business Process in my new repository but I can edit them for a Business Process on the same server in a different repository. Same for logging into the Live Event Viewer - I can use windows auth for the old repository but not the new. I have all rights and privileges in the new repository and I can login to it and perform security configuration, so what right could I still missing on the new repository?

0 0

replied on May 6, 2015

Can you log into the new repository with Windows Authentication from the Client?

0 0

replied on May 6, 2015 • Show version history

Yes, logging into the client has never been a problem.

And as I mentioned below (sorry about the two threads...) by switching the Authentication setting on the properties of my AD group from 'Inherit' to 'Trust' that allowed me to edit starting rules and get past all the login issues I was having within the workflow environment, such as monitoring the new repository. But still no visible business processes.

One odd thing that I notice is that my user account isn't automatically added to the "Windows Accounts" node in this new repository after I login like it does in every other repository. Also I used the same workflow profile name on the Prod server as I had on Test - is that a problem?

0 0

replied on May 6, 2015

Update: So I found a difference in my rights in the new repository compared with the existing one. Under Users & Groups/Windows Accounts, in my group properties, I had Authentication set to: Inherit from group memberships. (I was able to log in, so I figured this setting was irrelevant for groups.) I changed it to "Trust: Allow Access" and now I am able to edit the starting rules of the business process (and live event viewer).

With that done, I added a description to business process, made a small change to one of the activity descriptions so it could be re-published, and re-published. But it still doesn't appear in the client. :-(

0 0

You are not allowed to follow up in this post.

Question

Question

Business processes not available after migrating to production

Answer

Replies

Sign in to reply to this post.