Skip to Content

To All SAP Agentry/SMP 3.0 users,

SAP Global Services and Support (GSS – One Service) tries to be proactive in knowledge sharing to the customers.

Based on some internal and external discussion with customers, partners and SAP consultants, general knowledge on what is known may be needed to be provided to prevent additional wasted work being done by customers or system integrators or users to prove that an issue exists.

  • The goal of the Agentry Support News (X-Month Year) is to make the customer know what issues and fixes are in the pipeline based on the given date
  • By knowing what is known, this proactively helps the customer or users of Agentry (in SMP 3.0) know what are the known issues to mitigate the time spent on analyzing and proving to SAP that an issue exist as the issue is already known and the fix forthcoming
  • There is no need to let SAP know of the issue (or no need to open an incident) – this will save precious time for both user/customer/partner and SAP
  • The forthcoming fix will be targeted on a newer release based on the specified current release below. It may be the next Patch Level or Patch Level +N or SP Level)

Current Date: 09/01/2015 (September 1)

Current SP Release Runtime: (Agentry Server – SMP): SMP 3.0 SP08

Current SP Release SDK: (Agentry Editor and Clients): SMP 3.0 SP09

Disclaimer: The data in here may change without notice and due care is required when referencing it. Do not use the data in here as reference when purchasing software, hardware or services in SAP or external parties. Some of the data may be purposely removed as it may be tied to new features that are not readily to be shared publicly and may only be shared in major announcement or official documentation. An actual date of release will not be provided to safeguard SAP in presenting a date. Not all known issues and fixes will be presented in this news article.

SAP Global Support proactively tries to partner with SAP users/customers/partners to generate information that can be shared to improve our software and services. We as the community of SAP users need to help each other by sharing the known fixes and knowledge to help strengthen the bond and speed of innovation.


Reactive to proactive, SAP support is best in class.

Before: Customers have a problem (issue) and need to ask SAP – Is this a known issue?


/wp-content/uploads/2015/09/problem_781703.png

Now (Agentry Support News – Month – Year): Helping the customer not to report an issue when the fix is forthcoming


/wp-content/uploads/2015/09/problem2_782432.png

Blog Rule: Any question about more details on the data below, you may respond to this blog. Keep it only to the subject header presented (do not ask for dates or version numbers as those can change or anything outside what is listed). For example, if you need more information on a line item specify the reference number and title, the author of this article may respond when available. Any other details you may refer to the disclaimer above.


Data as of September 1, 2015:

                                                                                            

                                                                                            

Issues with forthcoming fixes

[REFERENCE-3366] – Successful Login Action

[REFERENCE-3843] – Document Selection screen size is too small on iOS client

[REFERENCE-3859] – Complex Table Tree picker selects values too early and no way to cancel – WPF client

[REFERENCE-3938] – [Editor] Unable to get values from Response Header using OData Back-end

[REFERENCE-4075] – WPF Tile Inline Add Creates Ghost Tile at End of List

[REFERENCE-4242] – WPF-Scrolling down and then up on Complex Table Search dialog causes the “-NONE-” entry to have values in fields that were initially (and supposed to be) blank

[REFERENCE-4245] – Complex Table Drop Down controls are empty on WPF

[REFERENCE-4359] – WPF client button label by rule does not refresh

[REFERENCE-4364] – Typing into Android string field is not reflected on the screen

[REFERENCE-4546] – Incorrect screen animation invoked by OpenUI

[REFERENCE-4733] – Tile edit button not showing on WPF client

[REFERENCE-4789] – Google Maps in an HTML control on WPF client does not display special characters

[REFERENCE-4867] – Hyperlink Style on WPF Client

[REFERENCE-4922] – Half-width Japanese characters are only partially displayed

[REFERENCE-4923] – Android Branded client crashes when switching networks

[REFERENCE-5209] – Transactions unnecessarily orphaned during collection replacement

[REFERENCE-5218] – Close stale sockets after server timeout value is met

[REFERENCE-5231] – Backend-initiated lockouts don’t work

[REFERENCE-5233] – User is able to delete main screen set via Compare view

[REFERENCE-5319] – Add Support for Teamshare Session Logging

[REFERENCE-5523] – iOS client opens HTTPS URLs externally instead of HTML Control

[REFERENCE-5628] – Team Share – Export by tag does not import all changed values

[REFERENCE-5699] – Team Share – Updated images overridden after publish

[REFERENCE-5714] – WPF crashes when displaying tile list (disconnectedItem)

[REFERENCE-5715] – WPF platform caption doesn’t update on screensets

[REFERENCE-5717] – Android client crashes with an overlay view in landscape mode

[REFERENCE-5784] – Team Share – Renamed property treated as new property after update

[REFERENCE-5843] – GPS coordinates are inconsistently available on iOS

[REFERENCE-5904] – WPF ATE Stability Issues

[REFERENCE-5912] – Background sending in transmit hangs WPF client

[REFERENCE-5928] – “Close the screen set that the user is leaving” is working inconsistently

[REFERENCE-6017] – Android toolbar disappears after rotating device with Agentry in the background

[REFERENCE-6041] – Multi-screen tile display still shows object though no item is selected in Tile List

[REFERENCE-6043] – WPF External Data Field file browser filters on image types only

[REFERENCE-6046] – Editor – Sometimes the properties tab for an object doesn’t open

[REFERENCE-6047] – List Tile filter on WPF client is not refreshed following an object update

[REFERENCE-6048] – Android screen is showing check boxes when it should be clickable images

[REFERENCE-6053] – User Credential conflict when using multiple Agentry clients on iOS

[REFERENCE-6054] – List Selection field in iOS shows “is required” error

[REFERENCE-6058] – Keyboard header remains on screen after SlideOver activation in iOS 9

[REFERENCE-6059] – Location control not getting validated

[REFERENCE-6065] – Communication Error when using Turkish localization (Android Dev)

[REFERENCE-6066] – WPF client crash when running .bat file via Windows Command Action Step

[REFERENCE-6068] – Agentry buttons on iOS input controls are not picking up application tint style

[REFERENCE-6099] – “Swipe to Navigate” broken on Android

[REFERENCE-6100] – Clicking Scan button sometimes crashes the client

[REFERENCE-6142] – Team Share – Unable to complete Update

[REFERENCE-6144] – Action buttons and action menus overlap on iOS9

[REFERENCE-6357] – Unable to edit JavaScript Text rule terms via the middle rule editor pane

[REFERENCE-6359] – WPF client crash running an action following a canceled transaction

[REFERENCE-6393] – Team Share – Rule duplicated in tree after update

[REFERENCE-6401] – Agentry client text field allows only half of max length for Russian characters

[REFERENCE-6402] – Core – Creates database tables with invalid names

[REFERENCE-6403] – Android toolbar draws incorrectly following rotation

[REFERENCE-6441] – Fortify “Use after free” regression from WPF Client crashes when trying to end shift fix

[REFERENCE-6448] – Android client crashing with java.lang.OutOfMemoryError

[REFERENCE-6449] – Android client crashing intermittently with java.lang.IllegalStateException

[REFERENCE-6463] – WPF & iOS Rule based screens in a screenset does not get refreshed

[REFERENCE-6501] – Double click action results in “Collection not found” error on WPF client

[REFERENCE-6599] – Team Share – Editor freezes during update

[REFERENCE-6626] – Interacting with SP10 WPF ATE repeatedly crashes Eclipse

[REFERENCE-6702] – WPF client allows blank signature after the clear button is pressed for a required Signature Field

[REFERENCE-5504] – Client Crashed After selecting Exit button in Server URL selection dialog

[REFERENCE-5505] – client crashed after input invalid URL in server selection dialog

[REFERENCE-6002] – Image with 2 state or 4 state doesn’t work on toolbar button

[REFERENCE-6011] – Overflow toolbar doesn’t work on action button support

[REFERENCE-6579] – Error when executing batch build command for wpcordova client

 

Reference:


We hope by sharing this knowledge, you the customer may be able to save time and effort and continue to innovate to speed up configuration and deployment.

We may blog another Agentry Support News in the future with new data. Please stay tune.

Have a great day.

Mark Pe

SAP Platinum Support Engineer

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply