[jira] [Updated] (SYNCOPE-1325) Propagation Task log panel for AnyType default order to descending
[ https://issues.apache.org/jira/browse/SYNCOPE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filipe Silva updated SYNCOPE-1325: -- Fix Version/s: (was: 2.0.8) > Propagation Task log panel for AnyType default order to descending > --- > > Key: SYNCOPE-1325 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1325 > Project: Syncope > Issue Type: Improvement >Affects Versions: 2.0.8 >Reporter: Filipe Silva >Priority: Minor > > The Propagation Task log list for AnyType has default order by "Start Date" > ascending. > I think it should be descending and maybe order by "End Date" as in the Pull > Task Execution's List. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1325) Propagation Task log panel for AnyType default order to descending
[ https://issues.apache.org/jira/browse/SYNCOPE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filipe Silva updated SYNCOPE-1325: -- Affects Version/s: 2.0.8 > Propagation Task log panel for AnyType default order to descending > --- > > Key: SYNCOPE-1325 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1325 > Project: Syncope > Issue Type: Improvement >Affects Versions: 2.0.8 >Reporter: Filipe Silva >Priority: Minor > > The Propagation Task log list for AnyType has default order by "Start Date" > ascending. > I think it should be descending and maybe order by "End Date" as in the Pull > Task Execution's List. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1325) Propagation Task log panel for AnyType default order to descending
Filipe Silva created SYNCOPE-1325: - Summary: Propagation Task log panel for AnyType default order to descending Key: SYNCOPE-1325 URL: https://issues.apache.org/jira/browse/SYNCOPE-1325 Project: Syncope Issue Type: Improvement Reporter: Filipe Silva Fix For: 2.0.8 The Propagation Task log list for AnyType has default order by "Start Date" ascending. I think it should be descending and maybe order by "End Date" as in the Pull Task Execution's List. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1277) The "explore details" option for a resource doesn't show correctly non-text formats
[ https://issues.apache.org/jira/browse/SYNCOPE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filipe Silva updated SYNCOPE-1277: -- Affects Version/s: 2.0.8 > The "explore details" option for a resource doesn't show correctly non-text > formats > --- > > Key: SYNCOPE-1277 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1277 > Project: Syncope > Issue Type: Bug >Affects Versions: 2.0.7, 2.0.8 >Reporter: Filipe Silva >Priority: Minor > Attachments: Screenshot from 2018-02-23 16-02-39.png, Screenshot from > 2018-02-23 16-18-01.png > > > The display of details of a user attributes using the "explore" option for a > resource doesn't display the fields using the "formats" and so "non text" > fields are badly displayed > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518967#comment-16518967
]
Francesco Chicchiriccò commented on SYNCOPE-1321:
-
No worries [~moonworm]! I had some spare time yesterday, and jumped ahead, as
the time for 2.0.9 is approaching.
Looking forward to your further involvement.
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
