Location based usage tracking
Hi
Melissa
,
Something has come up over the past couple of weeks that is making me think we need to ticker a little bit more with how we produce usage details/reports for admin users in the new platform. Currently when we enter IP address ranges into the admin site, we also enter details on what location that IP address range is associated with in the comments field for the range: https://www.investorstatelawguide.com/subscribers/AddUser?id=454&group=42&status=-1&city=0
In certain cases, the IP range represents a proxy address coming from anywhere on the organization's network, but in most cases this can be associated with a specific office or location. Similar fields need to be added to the IP address ranges for the new ISLG: https://projects.invisionapp.com/share/6AOHL2Q9J8U#/screens/324768948) and https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/7381/silent
However, unlike the current admin site, these fields should be multi-entry, searchable dropdown fields that pull from the Location(s) - City entries added to the group.
In addition, the locations associated with IP address ranges should be integrated into the group session details: https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/5951/silent and https://projects.invisionapp.com/share/6AOHL2Q9J8U#/screens/324768953 as both a column in the session details table and a filter by location(s). This will enable us to understand better what offices are using ISLG, and generate the applicable reports as necessary.
Could we please update the applicable user stories and wireframes as necessary?
Also,
Guillaume
, please take note that similar features should be integrated into ILG.
Note I know things are getting a little crammed in the session details table, but perhaps we could remove the "Blocked" column, because I don't think we need to track this is the usage reports.
Thanks,
Morgan
Something has come up over the past couple of weeks that is making me think we need to ticker a little bit more with how we produce usage details/reports for admin users in the new platform. Currently when we enter IP address ranges into the admin site, we also enter details on what location that IP address range is associated with in the comments field for the range: https://www.investorstatelawguide.com/subscribers/AddUser?id=454&group=42&status=-1&city=0
In certain cases, the IP range represents a proxy address coming from anywhere on the organization's network, but in most cases this can be associated with a specific office or location. Similar fields need to be added to the IP address ranges for the new ISLG: https://projects.invisionapp.com/share/6AOHL2Q9J8U#/screens/324768948) and https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/7381/silent
However, unlike the current admin site, these fields should be multi-entry, searchable dropdown fields that pull from the Location(s) - City entries added to the group.
In addition, the locations associated with IP address ranges should be integrated into the group session details: https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiRUM0QzUwNTU4QzZBNUQ1NjQxRkNGNUQyM0FFRDQxM0YifQ==&boardPopup=userstory/5951/silent and https://projects.invisionapp.com/share/6AOHL2Q9J8U#/screens/324768953 as both a column in the session details table and a filter by location(s). This will enable us to understand better what offices are using ISLG, and generate the applicable reports as necessary.
Could we please update the applicable user stories and wireframes as necessary?
Also,
Note I know things are getting a little crammed in the session details table, but perhaps we could remove the "Blocked" column, because I don't think we need to track this is the usage reports.
Thanks,
Morgan