4 results found
-
allow potential service consumers to limit their usage authorization request to only the less sensitive resources
We're preparing the paperwork to request FWS authorization for one of our applications. Relative to other UW services, it's a fairly rigorous process, considering we only want org code and org name data, neither of which seems to be of a sensitive nature.
Since we're trying to follow best practices in terms of not re-using already approved certs across multiple applications, I anticipate we'll have to go through the approval process at least a few times.
It would be nice if we could self-regulate in exchange for a less rigorous authorization process - i.e. don't let us see sensitive stuff,…
23 votesWe definitely recognize this is a real problem. We plan on working with the FWS data stewards to see if we can develop a lighter weight process for certain resources.
-
Add BGT information to FWS
Add Budget information from BGT database to the Financial web service. This would provide data on current award amounts by account code.
5 votes -
Add financial transaction data to FWS
This would save us from having to manually download expenditure transactions from MyFinancial.Desktop.
Perhaps this effort could also expose other MyFD functions under web services, such as reconciliation.
2 votes -
Add salary benefit load rates to the Financial Web Service
At least a couple of UW systems require programmatic access to official UW benefit load rates. These rates are set annually by Management Accounting & Analysis and posted online for people to view and stored in the Financial Accounting System (FAS). If these rates were made available via FWS then UW systems could find the rates using a Web service instead of either copying the data locally or directly accessing a UW enterprise database.
1 vote
- Don't see your idea?