Hi all,
Below are my rough notes from today's Customer Connection Call for SAP NetWeaver Workflow 2015. Apologies for any and all typos. Misrepresentations are solely mine. I'd like to give a shout out to a few folks who have been instrumental in this project so far... FIRST alan.rickayzen, who has always had the back of Workflow people, ronen.weisz, who worked very hard to get this Customer Connection started, mike.pokraka2, who 'volunteered' to come up with tags which we will use to help categorize requests, martijn.wever2 and his colleagues from @VNSG, who are always ready to do some heavy lifting, and tammy.powlas3 who probably took much better notes than I did.
Workflow Customer Connection Call, Feb 13, 2015
The Invitation:
Agenda:
• Influencing via Customer Connection
• Focus Topic project timeline-scope
• Process & Tools
If you are interested in getting to know more details about the program please visit our collaboration site: Customer Influence.
Here you will find presentations and videos explaining the goals and process in detail.
Please use the web conference link and phone numbers below to dial in.
In case of any questions please do not hesitate to contact me upfront.
Heller, Daniel-Alexander daniel-alexander.heller@sap.com
Heike Kalwak is running the call.
First, some background blogs on this initiative:
The Workflow community has a great history of working hand and hand with SAP to get improvements to this tried and true (evergreen) technology implemented.
slide source: SAP
The recording will be posted on Influence.sap.com
Mandatory legalese:
ie: SAP is not making any promises, OK?
slide source: SAP
slide source: SAP
53 people on the call at this time. Since we are talking about an existing product (heck, it’s been in existence for almost 19 years, right?) - so we are in the Customer Connection phase, not the Customer Engagement or Co-Innovation Councils.
slide source: SAP
The development team evaluates all submitted improvements so not all requests will be implemented. Some may just not be feasible.
There will be milestone calls too. And via Influence.sap.com, continuous feedback loop where updates are posted.
Even if you are not interested in SAP Workflow, you should visit the Customer Influence site so you can see if there are improvements for the SAP areas you ARE interested in! (SAP Improvement Finder)
Alan Rickayzen takes over.
slide source: SAP
Gracious and charming and brilliant as always.
There have already been internal discussions in the development group as to what *they* would like to deliver as well.
About 50 requests so far. Based on development capacity (as well as the level of difficulty) requests will be prioritized
- Takeaway – Clean up your requests – be specific about the problem and the impact on end users and administrators, but don’t necessarily be trying to write the solution
The call was pretty much all developers, administrators, and SAP partners.
Alan praises us for long hours in development, but at the end of the day, a workaround may be feasible. Our users don’t care necessarily whether we had to type in extra code or extra bindings. So there will be a focus on the end user functionality and on the administrative tasks. That does not rule OUT enhancements to the development environment, as we all know that if a developer has to go to great lengths to achieve a solution - that will also make the usability and administration of the workflow more difficult.
For example: Inbox Column formatted according to dates in various geographical formats. We could all envision how this could be helpful, but it may be doable by workaround.
Workload analysis – who substitutes for whom – seems to make sense. – my 2 cents, after long years of doing this – substitution and trying to backtrack to see who was a substitute for whom at a specific period of time is very difficult.
Comment: florin.wach How particular requests are chosen…. Because it is important that the end user and the administrator have improvements – agreed. But asks also that the development for developers be improved because that makes it easier for the admin.
PROJECT TIMELINE:
slide source: SAP
We are starting the Collection Phase now. So far there are 57 improvements in the tool. The end of collection phase is April 2, 2015. The Selection Call will be in June 2015.
Takeaway: Get other customers to subscribe (at least 5 customers) to subscribe to your request.
Delivery Call December 2015!!!
Takeaway: Have your conversations about requests on the Influence.sap.com platform. That way, all customers and SAP developers can also see the conversions.
Request owners should be ready to be contacted to explain their requests in detail, and also to support the testing of these requests.
slide source: SAP
And a little chatting...
(g) Samuli Kaski: In the Customer Influence collaboration tool, would it be possible to categorize the requests, e.g. WF runtime, Inbox, Gateway, etc?
(g) Jake Schmidt: Analytics report....we've got SWI2_DURA, we don't need anything beyond that :wink:
(g) Mike Pokraka: Good point, at 50+ it's already getting messy. Perhaps we could use tags?
slide source: SAP
You submit it, you’re the owner. There is some expectation that you will act as a central point of contact, support the development phase, and optionally, become an active reference.
Mike Pokraka will develop a system of tags for request owners to use to help us categorize their requests.
slide source: SAP
g) Mike Pokraka: A few people already added tag, we should just try to standardise them and tag the existing requests
(g) Sue Keohan: @MIKE - Agreed. Are you taking an action item to come up with the tags? 🙂
(g) Mike Pokraka: Me and my big mouth, OK 🙂
(g) Sue Keohan: @MIKE - good lad.
(g) Sue Keohan: @MIKE - I am sure you can handle it. 🙂
(g) Mike Pokraka: No prob 😉
(g) Sue Keohan: Again, advice to all: Be very detailed (and use Mike's tags) when submitting your requests - or editing them. This will eliminate a lot of back-and-forth, and help everyone understand what the problem is and if we share that problem.
slide source: SAP
Using the Navigate To panel, click on Products, below Database and Technology you will find Business Process Management and Integration. And here you see nothing because you’re not logged on. You need to REGISTER!!!
Once you’ve logged in, you’ll see SAP NetWeaver Workflow 2015.
slide source: SAP
Example of a submitted request:
slide source: SAP
slide source: SAP
This is where the recordings will be – under documents and events.
Mark your calendars, March 26 for final call of collection phase.
slide source: SAP
More chat excerpts:
(g) Sue Keohan: Oh, and new request just came in! BSVW Support for OO ABAP (not just BOR)" (D8320) was added to the Focus Topic "SAP NetWeaver Workflow 2015
Alan Rickayzen: Yep... no traffice jam, and the tool is not Jam either (but I love both tools)
(g) Sue Keohan: How many people on the call right now???
(g) Jake Schmidt: I'm putting in more requests
(g) Samuli Kaski: Thank you all, have a nice weekend!
(g) Florin Wach (germany): thx & goodbye
Alan Rickayzen: about 50 Sue
(g) Sue Keohan: Thank you Heike - sorry to keep you so busy with the chat!!!
(g) Sue Keohan: Thanks alL! Lets get to work!!!!!!!
(g) Mike Pokraka: Thanks all
I think Mike said it best. Thanks all. I look forward to seeing how well all the WFers out there can collaborate and help make things even better.
- SAP Managed Tags:
6 Comments
