Where do you have the designer installed? On a seperate system or on the ServiceDesk 7 server?

It's on a separate machine. So I'm using three computers for this:
1. servicedesk server + workflow server + sql server
2. NS server
3. Workflow designer

What is the result if you run "License Status Manager" under the tray icon => shortcuts and click the "Run tests" button?
Also if you open "notification server credential manager" under shortcuts and run the test.

NS Credential test run successfully but not with the license status test. I got 3 items with failed result.
I notice that only those components from SD.Components.dll that have this problem.

Among those components are:
* Get All Changes Available As Template
* Submit Change Ticket
* Submit Incident
* Get Email Header And Footer
* Check And Changes SLA Requirements

Correct me if I'm wrong, these components are the default components from Workflow7 to modify SD7, aren't they?

EJ,

Did you ever find out what the problem was?

Hi. I can help you with this. Send me an email directly and we'll get to the bottom of it.

The licensing for ServiceDesk is complicated because it layers on top of the licensing engine for the Workflow platform. There are two components to this, which are reflected by the tabs in the licensing status tool. The first screen shows you what capabilities are authorized by the current license level of the Workflow platform. The second tab shows any additional applications which are modifying or overruling the current Workflow license. In this case, the ServiceDesk application is doing so. An application like ServiceDesk is recognized by the Workflow licensing engine as a "Service Context".

In addition to modifying the license state of the workflow server, a service context license also protects any components, web parts, exchanges, and other objects that are provided by the application. In the case of ServiceDesk, there are quite a few components that are delivered as part of the application. These components are bound to the ServiceDesk service context, which means that they are validated by the following rules:

1. They may only be used in ServiceDesk workflow processes. In other words, you cannot drag one of these components onto a non-servicedesk process and use it.
2. They will remain invalid unless the service context license provider that they are bound to is present on the machine and is returning a valid license.

All licensing assemblies are found in the [Workflow Install]\Server Extensions\Plugins directory. You should see the workflow platform licensing driver here as well as a service context license provider for ServiceDesk. If you do not see the ServiceDesk assembly, you cannot edit the ServiceDesk processes on that machine.

This may be a bug. I'll have to find out if we are installing the ServiceDesk license provider if only the workflow designer role is selected. If we are not, the workaround is as follows:

1. Make sure the designer machine's default NS is set to the NS on which the ServiceDesk solution is installed.
2. Copy the servicedesk license provider assembly from the ServiceDesk server (in the directory mentioned above) to the designer machine in the same directory.
3. Restart Server Extensions on the designer machine and reopen the designer.

Hope this helps.

I am now able to use those components. I figured out that if I check the "Generate new session ID" checkbox when I open the package, it will make those components having the error message. There's something about generating new session ID that if I use a new session ID it will not link to current process which I want to customize.

This error can also be caused if you tried to add a serviceDesk component like "submit change ticket" inside the primary model in the project. To use such components that aren't standard components of Workflow type project, you'll need to encapsulate them inside a sister model that you can just create. Then you'll use a "Linked model" component inside the primary model as a shortcut (place holder) to the new model you just created that includes the "submit change ticket" component.