HIPO Configuration

The HIPO Configuration screen allows you to configure the thresholds for the number of different types of HIPO jobs that can be run at the same time. By default, the thresholds are set to a low value, which ensures that all jobs are run as a HIPO job. This means that users always have to wait for the HIPO job to complete and they can see the progress of the job in the editing screen. If you have a powerful server, you can configure your system so that less intensive jobs run immediately and not as a HIPO job.

If the number of assets that are being processed by a HIPO job is less than the threshold entered, a HIPO job will not appear within the editing screen. If the number of assets is more than the threshold, a HIPO job will appear but it will only be refreshed once the set number of assets has been processed. For example, say you set the Edit Status Threshold to 20. If you change the Status for 19 assets, no HIPO job will appear as it is below the threshold. If you change the Status for 100 assets, a HIPO job will appear but will only be refreshed 5 times (i.e. once for every 20 assets it processes). By default, if this threshold was not changed, it would refresh 100 times (i.e. once for each asset it processes).

To access the HIPO Configuration screen, click on the System Configuration System config icon icon in the top right hand corner of the screen – a drop down list will appear under this icon. From this list, select HIPO Configuration – the screen will appear. The HIPO Server Configuration section of the screen is shown in the figure below.

The HIPO Server Configuration section of the HIPO Configuration screen
The HIPO Server Configuration section of the HIPO Configuration screen

The fields that are available on this screen are outlined below.

  • Run on Squiz Server: select whether or not to run the HIPO jobs on the Squiz server. This requires the Squiz Server to be set up within Squiz Matrix. For more information on the Squiz Server, refer to the Squiz Server chapter in this manual.
  • Squiz Server Status Check Threshold: enter the number of seconds that the system should wait before querying the server as to the job's status.
  • Freestyle Threshold: enter the threshold for the percentage of the total number of HIPO processes. For example, say you set this field as 80%. You then have a job running that uses 50% of a particular set threshold and another job that also uses 50% of another set threshold, giving a total of 100%. Because you have exceeded the Freestyle Threshold of 80%, the job will be run as a HIPO. Please note that this field can have a value of over 100%.
  • Acquire Lock Threshold: enter the threshold for the number assets that can be locked by a user without a HIPO job being spawned.
  • Clear Cache Threshold: enter the threshold for the number of assets that can have their cached cleared by a user without a HIPO job being spawned.
  • Clone Asset Threshold: enter the threshold for the number of assets that can be cloned by a user without a HIPO job being spawned.
  • Edit Metadata Threshold: enter the threshold for the number of assets that can be updated by a user cascading metadata, without a HIPO job being spawned.
  • Permissions Threshold: enter the threshold for the number of assets that can be updated by a user cascading permissions, without a HIPO job being spawned.
  • Edit Status Threshold: enter the threshold for the number of assets who’s Status can be changed, without a HIPO job being spawned.
  • Edit Tag Threshold: enter the threshold for the number of tags that can be changed, without a HIPO job being spawned.
  • Workflow Schemas Threshold: enter the threshold for the number of assets that can be updated by a user cascading workflow schema, without a HIPO job being spawned.
  • Purge Trash Threshold: enter the threshold for the number of assets that a user can purge from the trash, without a HIPO job being spawned.
  • Metadata Regeneration Threshold: enter the threshold for the total number of assets that can be updated by a user regenerating metadata, without a HIPO job being spawned.
  • Trigger Execution Threshold: enter the threshold for the number of triggers that can be executed, without a HIPO job being spawned.
  • Lookups Updating Threshold: enter the threshold for the number of assets that can be updated by a user updating a URL, Web Path or applying a Design, without a HIPO job being spawned.
  • File Import Threshold: enter the number of file assets that can be created when you are performing a file import, without a HIPO job being spawned.

Previous Next