Page Comparison

...

Okay, but how can you add a custom attribute, a custom field, or a custom column that will show you if you need or don’t need to do some actions? Again, let’s use the postprocessing!

There is one small nuance: postprocessing transforms properties of a record object one by one in the order of a list you have in result table attributes. This means that if you apply data transformation (data postprocessing) to your record in one attribute, the next attribute will contain a modified record. Let's see what it looks like after the record object in the login expiration time attribute has been updated.

...

Here you see that there is already a value for the appropriate key—login expiration time—in the postprocessed format, so the data has already been transformed. But it is also to see that the object was extended with a JSON string that contains a basic, unchanged record. And in the new postprocessing function, you can use either the already modified data or the raw.

...

The JavaScript function, which will add a note with a conclusion for the current user, has been prepared. It will show you if next month there will be users whose login will expire. Thanks to this function, you will get data about the number of days before the login expiration or a message that a login has already expired.

...

Let's implement this postprocessing function to a custom field named “conclusion.” The postprocessing and the “Pass full record object to the postprocessing function” feature are enabled. This is because you need another attribute for this functionality. Let's save and run the report.

...

Today’s date is the 18^th of December and a login for this user will expire in 29 days.

...

This one will expire in about a month or later, and some logins have already expired.

...

For the expired logins, you need to decide either to extend or archive them. Maybe you need to do some other actions. This is one of the clear and simple ways you can use postprocessing.

The other ones are for attributes that contain numeric values like the XML state of drivers. Let's check driver state changes in the dashboard.

...

As you can see here, there were some state changes for drivers during the last week. And changes appear with changes in numeric values of statuses.

...

Of course, you can memorize and decode what each number means, but much easier will be to transform these numbers into a readable format using postprocessing. You can check it in the default NetIQ Audit Driver status report.

...

It is transformed into a readable format, and we can check what the postprocessing function looks like.

...

Should you have any questions or require any assistance, please do not hesitate to contact us at any time swsupport.skypro@skypro.ch