You can use the following StoredIQ® for Legal tool
scripts to check and eventually change the size of string attributes.
About this task
The scripts must be run inside the WebSphere® Application
Server container on the StoredIQ for Legal virtual machine.The
following limitations apply:
- Only custom attributes of the following data types are supported:
- String
- Date range (single)
- Date ranges (multiple)
- Drop-down list (single-select and multiple-select)
- Combination box (single-select and multiple-select)
- Radio button
The following data types are not supported:
- Number
- Date
- Boolean
- Object list (single-select and multiple-select)
- Attachment (single)
- Attachments (multiple)
- You cannot change the size of built-in attributes. Trying to do so results in an error.
- You can reduce the attribute size only to the already consumed size. Trying to reduce it further
results in an error.
Complete these steps on an OpenShift®
client that has access to the cluster where IBM®
StoredIQ for Legal is deployed.
Procedure
- Complete these steps depending on your deployment type:
For StoredIQ for Legal (VM):
- Sign in to the StoredIQ for Legal VM as
root.
- Open the WebSphere Application
Server container by
running this command:
docker exec -it ilg_sol_plugin bash
For StoredIQ for Legal
(Container), complete these
steps on an OpenShift client that has access
to the cluster where IBM
StoredIQ for Legal is deployed:
- Obtain the name of the
ilg-sol-plugin container by running this
command:
CONTAINER_NAME=$(oc get pods -n siq4lopenshift -l app=ilg-sol-plugin -o name | sed "s/^.\{4\}//")
- Open the
ilg-sol-plugin container by running the following command.
Replace $CONTAINER_NAME with the name returned in the previous step.
oc exec -it $CONTAINER_NAME bash
- Change to the directory where the scripts are stored by running this command:
cd /opt/ibm/ilg-sol-toolkit/scripts
- Run one of the following commands.
- To check the attribute size, run this command:
./get_max_string_size.sh
entityNameThe output shows all custom string attributes within the
specified attribute category by name, and the allocated size and the maximum consumed size for each
attribute.
Sample command: ./get_max_string_size.sh datarequest
- To change the attribute size, run this command:
./change_string_field_size.sh
entityName
attributeName
newSizeSample command: ./change_string_field_size.sh
datarequest ca_attribute1 10
The parameters are as follows:
- entityName
- One of the following values:
| entityName |
Type of attributes |
| datasource |
Data source |
| datasourceapplication |
Application |
| datasourceserver |
Server |
| datarequest |
Data request |
| fulfillmentitem |
Fulfillment item |
| fulfillmentworkpackage |
Work package |
| interview |
Interview |
| matter |
Matter |
| notice |
Hold notice |
| noticedraft |
Hold notice (draft) |
| noticehistory |
Hold notice (history) |
| persondistinct |
Person |
- attributeName
- The name of the attribute for which you want to change the size.
- newSize
- The new size to apply to the attribute. The minimum size for an attribute must be calculated as follows:
- For single-select attributes:
size of the longest option * number of options +
100
- For multiple-select attributes:
size of the longest option + 100