Would you ask the Commvault if they can increase the number of characters allowed in Commvault VSA subclient description field to 10,000

Â
Would you ask the Commvault if they can increase the number of characters allowed in Commvault VSA subclient description field to 10,000
Â
That seem’s unreasonable… why would you need 10,000 characters for a description?
That's more like a treatise.
Â
There are short stories that use less than 10,000 characters.
What about 6000 characters ?
Â
If as I see many customers doing, notes on changes being made. We have an Audit tab option which can be used to track this in a much better way. ie the details can’t be doctorred etc…
Would that work for you?
I have seen people use descriptions as pseudo-tags, instead of actual tags, which to be fair is a relatively new feature
Audit tab option as in pull a report ?
pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like
Audit tab option as in pull a report ?
pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like
I don’t have screenshots but people have posted it where in the description field they would do something like so.Â
CompanyName = MyCompany
TenantName = Tenant1
BillingID = 4001
Essentially using the description as a way to add tags to different parts of the hierarchy.Â
This of course then requires large description fields and some method of parsing the description text.
Since tags are now supported this shouldn't be necessary anymore
Audit tab option as in pull a report ?
pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like
HelloÂ
Not the report. If you look at the properties of client you will see there is an audit tab.
You can add information in there and set a severity etc. But it is a write once read type of setting so give you an historical record of what is changing on the client. Very useful way to avoiding using the description field as a way to track changes. These are limited to 256 characters though but usually enough to detail what has changed.
If you are looking to automate it, using the workflow engine you can use the execute command:
and then add some XML like so:
<App_SetEntityAuditReq>Â
   <entity _type_="3" clientName="xpath:{/workflow/inputs/client}"/>Â
   <entityAuditList notes="add your information you want to record here" severity="1">
      <user userId="xpath:{/workflow/system/executor/userId}" userName="xpath:{/workflow/system/executor/userName}"/>Â
   </entityAuditList>
</App_SetEntityAuditReq>
As for tags, these are managed in Command Center.
And if you want to automate these then use the API:
PUT https://{{serverUrl}}/Tags
{
 "entityTag":
  {
   "entityId": 279,
   "entityType": 3,
   "tag":
    {
     "name": "name1",
     "value": "value1"
    },
    {
     "name": "name2",
     "value": "value2"
    }
   ]
  }
 ]
}
Tags a useful to then make use of to add to Client groups, plans, include in reports etc...
Audit tab option as in pull a report ?
pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like
HelloÂ
Not the report. If you look at the properties of client you will see there is an audit tab.
You can add information in there and set a severity etc. But it is a write once read type of setting so give you an historical record of what is changing on the client. Very useful way to avoiding using the description field as a way to track changes. These are limited to 256 characters though but usually enough to detail what has changed.
If you are looking to automate it, using the workflow engine you can use the execute command:
and then add some XML like so:
<App_SetEntityAuditReq>Â
   <entity _type_="3" clientName="xpath:{/workflow/inputs/client}"/>Â
   <entityAuditList notes="add your information you want to record here" severity="1">
      <user userId="xpath:{/workflow/system/executor/userId}" userName="xpath:{/workflow/system/executor/userName}"/>Â
   </entityAuditList>
</App_SetEntityAuditReq>
That audit note thing is genuinely useful.Â
Thanks.
thank you
Â
Audit tab option as in pull a report ?
pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like
HelloÂ
Not the report. If you look at the properties of client you will see there is an audit tab.
You can add information in there and set a severity etc. But it is a write once read type of setting so give you an historical record of what is changing on the client. Very useful way to avoiding using the description field as a way to track changes. These are limited to 256 characters though but usually enough to detail what has changed.
If you are looking to automate it, using the workflow engine you can use the execute command:
and then add some XML like so:
<App_SetEntityAuditReq>Â
   <entity _type_="3" clientName="xpath:{/workflow/inputs/client}"/>Â
   <entityAuditList notes="add your information you want to record here" severity="1">
      <user userId="xpath:{/workflow/system/executor/userId}" userName="xpath:{/workflow/system/executor/userName}"/>Â
   </entityAuditList>
</App_SetEntityAuditReq>
That audit note thing is genuinely useful.Â
Thanks.
Â
Hey! How can this be done using the APIs?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.