Working with cases

You can perform the following actions on cases in File Explorer:


Create case

You can create new cases in File Explorer by creating new subfolders in the following folders:

  • Open cases
  • Unclassified cases
  • Case folders

When you create a new case through WorkZone Explorer, the case is automatically created in a temporary case group named SJ-TEMP. You can change the case group and other required information later by using WorkZone Client. Cases that are created in SJ-TEMP are automatically added to the Unclassified cases folder regardless of where they were created.

If your organization only uses facets and not case classes, you can configure WorkZone Explorer to add a specific case class as the default case class.

Important: The create case functionality is not available by default. Case creation must be enabled on the SJ-TEMP case class in WorkZone Configuration Management.

 

Create child cases

You can create child cases in File Explorer in two ways:

  • Move a case folder to another case folder. The case folder that you move becomes a child case.
  • Create a new folder in a case folder. The new folder becomes a child case. The child case inherits the file class and access code of the parent case.


Rename cases

You can rename a case by renaming the case folder.


Add or remove cases to the Favorite cases folder

You add cases to the Favorite cases folder by dragging and dropping case folders into the Favorite cases folder.

To remove a case from the Favorite cases folder, drag and drop the case folder into the Recycle bin folder.

The case is not deleted. It is only removed from the Favorite cases folder.


Date Modified on Cases

The Date Modified field for a case is updated automatically in File Explorer when documents on the case are changed or when documents are added to or removed from the case.

Sometimes, it may look as if a user has updated a case without having correct access rights. This happens when the user has access to a document on the case but not to the case itself, for example, when a user edits a document that is not protected by the case and the user does not have update access to the case. This is standard behavior and does not represent a security issue.