Security Tokens missing on package import

Issue

When importing a package that should contain Security Tokens, the tokens are not successfully imported.

 

Cause

This can be due to a known software defect in the Export process of the Security Tokens.  If the exported package is a SCNJ (Scan Create New Job) Form OR the SCNJ Form is a part of the overall package, then the Security Tokens are not exported.

Solution

The workaround would be to export the Security Token as part of a standard Form, and then update the SCNJ form in the target environment to use that same token.  

Issue is submitted under TFS Bug ID: 1774981.

Level of Complexity 

Easy

 

Applies to  

Product	Version	Build	Environment	Hardware
KTA	7.10

References

Add any references to other internal or external articles

 

Article # 3039287