x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 87 subscribers
  • Views 1348 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
44
topics
90
replies
Payroll, Time Tracking, and Job Cost
776
topics
1k
replies
Reporting and Analytics
960
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
tnwcpa

Alerts and Workflow with Payroll 2.x

SUGGESTED
Posted By

Currently utilize Alerts & Workflow to notify us when somebodies birthday and/or work anniversary date is forth coming, however with the new constraints on PII within PR 2.x, it has essentially rendered these alerts worthless.

Can't really seem to get a great answer out of either Sage or Vineyardsoft.  I did receive this response from the Sage expert at Vineyardsoft via their Sage liaison regarding this issue:

“Sage Alerts & Workflow accesses Sage 100 data via an ODBC connection. PII employee payroll data is encrypted and not accessible via ODBC, this has been documented since the initial release of Payroll in 2017. Development partners wishing to access unencrypted PII employee payroll data must use Sage 100 business objects to decrypt and retrieve the data.”

Not really certain on how to utilize BO within Alerts & Workflow.

  • 0

    Pain in the butt isn't it?   I understand the why, but it sure makes things tough trying to do custom reports.

    The only possibility I could think of is to create UDF's that mirror the data although the data would probably have to be manually input.  Of course this also causes data security issues as well.

  • 0 in reply to TomTarget

    I would think that a UDF to hold birthday and hire date is hardly data that needs to be secure.

  • 0

    Yeah, you wouldn't think that would be classified as PII, but so is the case.

    Just rendered all Alerts for this customer worthless.  Think that somebody would have figured out how to decrypt similar to how you now have to in a custom crystal report.

    VERY FRUSTRATING!

  • 0 in reply to tnwcpa
    SUGGESTED

    Just a crazy shot it the dark but perhaps you could set up a VI export and schedule it using Library Master > Main > Task Scheduler and then use Sage Alerts to read the CSV (or whatever output file you decide to use). This might get dicey with the number of license database connections in Sage Alerts though since you would need to set up a DSN to read the CSV file. 

    Alternative is similar to Tom's answer, could have a UDT containing just the bare minimum of the data you want to use in the query but not sure how this would affect compliance or what the results would be if you were found to be not be compliant by doing this.

    You could update the UDF or UDT by using a VI export and VI import or manual entry as Tom said.

*Community Hub is the new name for Sage City