Skip main navigation (Press Enter).
Log in
Toggle navigation
Log in
Community
Topic Groups
Champions
Directory
Program overview
Rising Champions
IBM Champions group
User Groups
Directory
Benefits
Events
Dev Days
Conference
Community events
User Groups events
All TechXchange events
Participate
TechXchange Group
Welcome Corner
Blogging
Member directory
Community leaders
Resources
IBM TechXchange
Community
Conference
Events
IBM Developer
IBM Training
IBM TechXchange
Community
Conference
Events
IBM Developer
IBM Training
Planning Analytics
×
Planning Analytics
Get AI-infused integrated business planning
Group Home
Threads
7.6K
Blogs
405
Events
1
Library
236
Members
3K
View Only
Share
Share on LinkedIn
Share on X
Share on Facebook
Back to Blog List
Upload files with action buttons in Planning Analytics Workspace 2.0.77
By
STUART KING
posted
Tue May 17, 2022 12:54 PM
Like
This video demonstrates the new file upload feature for action buttons in Planning Analytics Workspace 2.0.77.
This feature allows end users to upload files to be used as a data source for a Turbo Integrator process. This new capability should be used as a replacement if the classic Turbo Integrator editor widget was being used to support users uploading files as a data source. The file name can be passed as a string parameter value to the Turbo Integrator process to support different file names. Assuming a string parameter pFileName the following code can be used in the prolog procedure to set the file data source to the uploaded file.
#PlanningAnalyticswithWatson
2 comments
39 views
Permalink
Copy
https://community.ibm.com/community/user/blogs/nickolus-plowden/2022/05/17/paw-action-buttons
Comments
George Tonkin
Sun June 12, 2022 04:58 AM
Thanks Stuart - very useful feature for us. Next is the ability to upload an XLSX and have PAW do the necessary conversions in the background.
@Mark Wragg
- looks to be any variable - the linkage is done when assigning the Control Type as File to the parameter.
Mark Wragg
Tue May 31, 2022 11:04 AM
Hi Stuart,
thanks for this.
Couple of questions (and apologies if I misunderstood anything or the questions appear dumb),
We have noticed that if you create a process in Architect and then modify it in PAW the process can become corrupted.
Am I correct in thinking that this feature should only be applied to processes that were originally created in PAW?
Does it go without saying that pFileName is now a sort of reserved parameter name that should be avoided in processes?
regards,
Mark
Powered by Higher Logic