Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ParameterRequiredTypeDescription
${featureId}YesintegerSpecifies feature-specific parameters.
${returnType}YesstringSpecifies the format in which license usage data should be returned. The format can be one of the following: json, csv, xls or pdf.
sdYesstringSpecifies the start date for which the report will be generated in YYYY-MM-DD format; for example, 2016-01-20.
edYesstringSpecifies the end date for which the report will be generated in YYYY-MM-DD format; for example, 2016-01-27.
granularityYesinteger

Specifies granularity of the returned data; Can be one of the following:

  • quarter - 2
  • month - 3
  • week - 4
  • day - 5
  • hour - 6
rnNostringSpecifies the name of the report that will be displayed once the report has been exported to PDF or Excel.
filterNojson/string

Applies filtering license usage data on all fields.

To filter by string column, use the following format: 

Code Block
languagejs
[
	{ 
		"type": "string",
		"field": "lud",
		"value": "${value}"
	}
]

To filter by numeric column, use the following format:

Code Block
languagejs
[
	{ 
		"type": "numeric", 
		"comparison": "${gt | lt | eq}", 
		"field": "${lumin | lua | lumax | lbmin | lbmax | ldtc | hu | ft}",
		"value": "${value}" 
	}
]


fieldsVisibilityNojson/string

Specifies field visibility settings, for example:

Code Block
languagejs
{ 
	"lud": "1", 
	"lumin": "1", 
	"lua": "1", 
	"lumax": "1", 
	"lbmin": "1", 
	"lbmax": "1", 
	"ldtc": "1", 
	"hu": "1", 
	"ft": "1"
}


where number "1" indicates that a specific field is visible, ''0" indicates it is not.

Note that the order of the settings you make is important – when exported, the fields will be visible in exactly the same order you specify here.

limitNointegerDetermines the maximum number of data records that can be returned. The value must be greater than zero.
offsetNointegerSpecifies the offset of the first row to return.
orderByNostring

Specifies the field by which you want to order your data records. The field name can be one of the following:

 

lud | lumin | lua | lumax | lbmin | lbmax | ldtc | hu | ft
orderDirectionNostringDetermines whether the sorting results will be displayed in ascending (ASC) or descending (DESC) order.

If your request is successful, you should see a response similar to the following:

Code Block
languagejs
{
  	"success": ${success},
  	"msg": ${message},
  	"data": [
    	{
      		"fid": ${featureId},
      		"lud": ${date},
      		"lumin": ${minUsed},
      		"lua": ${averageUsed},
      		"lumax": ${maxUsed},
      		"lbmin": ${minBorrowed},
      		"lbmax": ${maxBorrowed},
      		"ldtc": ${denials},
      		"hu": ${hoursUsed},
      		"ft": ${total}
    	}
  	],
  	"code": ${code},
  	"totalCount": ${count}
}

where the response fields can be explained as follows:

...

If your request is successful, you should see a response similar to the following:

Code Block
languagejs
{
  	"success": ${success},
  	"msg": ${message},
  	"data": [
    	{
      		"fid": ${featureId_1},
      		"lud": ${date},
      		"lumin": ${minUsed},
      		"lua": ${averageUsed},
      		"lumax": ${maxUsed},
      		"lbmin": ${minBorrowed},
      		"lbmax": ${maxBorrowed},
      		"ldtc": ${denials},
      		"hu": ${hoursUsed},
      		"ft": ${total}
    	},
		{
      		"fid": ${featureId_2},
      		"lud": ${date},
      		"lumin": ${minUsed},
      		"lua": ${averageUsed},
      		"lumax": ${maxUsed},
      		"lbmin": ${minBorrowed},
      		"lbmax": ${maxBorrowed},
      		"ldtc": ${denials},
      		"hu": ${hoursUsed},
      		"ft": ${total}
    	}
  	],
  	"code": ${code},
  	"totalCount": ${count}
}

The meaning of all fields are the same as in Usage History For Feature.

...

ParameterRequiredTypeDescription
${lsid}YesintegerLicense Server Id.
${returnType}YesstringSee Usage History For Feature.
sdYesstringSee Usage History For Feature.
edYesstringSee Usage History For Feature.
granularityYesintegerSee Usage History For Feature.
rnNostringSee Usage History For Feature.
filterNojson/string

Applies filtering license usage data on all fields.

To filter by string column, use the following format: 

Code Block
languagejs
[
	{ 
		"type": "string", 
		"field": "${lud | fns | fv | ftype}",
		"value": "${value}"
	}
]

To filter by numeric column, use the following format:

 

Code Block
languagejs
[
	{ 
		"type": "numeric", 
		"field": "${lumin | lua | lumax | lbmin | lbmax | ldtc | hu | ft}",
		"value": "${value}"
	}
]


fieldsVisibilityNojson/string

Specifies field visibility settings, for example:

Code Block
languagejs
{ 
	"lud": "1", 
	"lumin": "1", 
	"lua": "0", 
	"lumax": "1", 
	"lbmin": "1", 
	"lbmax": "1", 
	"ldtc": "1", 
	"hu": "0", 
	"ft": "0",
	"fns": "1",
	"fv": "1",
	"ftype": "1"
}

 

where number "1" indicates that a specific field is visible, ''0" indicates it is not.

Note that the order of the settings you make is important – when exported, the fields will be visible in exactly the same order you specify here.

limitNointegerSee Usage History For Feature.
offsetNointegerSee Usage History For Feature.
orderByNostring

Specifies the field by which you want to order your data records. The field name can be one of the following: 

lud | fns | fv | ftype | fid | lumin | lua | lumax | lbmin | lbmax | ldtc | hu | ft
orderDirectionNostringSee Usage History For Feature.

If your request is successful, you should see a response similar to the following: 

Code Block
languagejs
{
	"success": ${success},
	"msg": ${message},
  	"data": [
    	{
      		"fid": ${featureId_1},
      		"lud": ${date},
      		"lumin": ${minUsed},
      		"lua": ${averageUsed},
      		"lumax": ${maxUsed},
      		"lbmin": ${minBorrowed},
      		"lbmax": ${maxBorrowed},
      		"ldtc": ${denials},
      		"hu": ${hoursUsed},
      		"ft": ${total},
			"fns": ${featureName},
			"ftype": ${featureType},
			"fv": ${featureVersion}
    	},
		{
      		"fid": ${featureId_1},
      		"lud": ${date},
      		"lumin": ${minUsed},
      		"lua": ${averageUsed},
      		"lumax": ${maxUsed},
      		"lbmin": ${minBorrowed},
      		"lbmax": ${maxBorrowed},
      		"ldtc": ${denials},
      		"hu": ${hoursUsed},
      		"ft": ${total},
			"fns": ${featureName},
			"ftype": ${featureType},
			"fv": ${featureVersion}
    	}
  	],
  	"code": ${code},
  	"totalCount": ${count}
}

 

where the response fields can be explained as follows:

 

FieldTypeDescription
successbooleanThis field indicates that the API request was successfully processed.
msgstringError message returned on failure.
fidintegerFeature Id
ludstringFor Granularity hour - Datetime, for rest Date, which indicates point int time that data are about.
luminintegerMinimal licenses used count for given date.
luafloatAverage licenses used count for given date.
lumaxintegerMaximum licenses used count for given date.
lbminintegerMinimal licenses borrowed count for given date.
lbmaxintegerMaximum licenses borrowed count for given date.

ldtc

integerDenials count.
hufloatHours used.
ftintegerTotal.
codeintegerError code if success == false, null otherwise.
totalCountintegerTotal number of rows returned.
fnsstringFeature name.
ftypestringFeature tyep.
fvstringFeature version.